Debug Tunnel.appEx on mac Designed for iPad

Does someone know how to debug ios app on mac designed for iPad? i can debug on real iOS device but cant attach Tunnel to work for mac.

Answered by DTS Engineer in 835421022

This is a packet tunnel provider, right? If so, be warned about our advice in TN3120 Expected use cases for Network Extension packet tunnel providers.

Also, if you using Go, make sure you have a main executable UUID. Without that, you’ll likely encounter weird problems. See TN3178 Checking for and resolving build UUID problems.

Returning to your core problem, you could create a temporary macOS app with a macOS packet tunnel appex embedded within it. That’ll likely improve your debugging experience.

IMPORTANT macOS supports both appex and sysex packaging for packet tunnel providers. See TN3134 Network Extension provider deployment. Most folks use the sysex packaging on the Mac, but in this case you specifically want the appex packaging.

it has 50MB memory limit

I presume that you only bump into this limit with debug builds of your product? Because you’ll eventually need to deploy this product to iOS, and there’s no avoiding the limit then.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Does someone know how to debug ios app on mac designed for iPad?

Gotta admit that I’ve never tried that. Honestly, it always struck me as miraculous that this technology works at all (-:

What’s the goal of this debugging effort? Is it that your provider works on an iOS device but fails on the Mac? Or are you just trying to optimise your workflow by not having to deal with the iOS device?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thanks for your reply! I am working on proxy utility that uses xtls xRay core (Go lang library) for secure internet surfing. I debug Tunnel on iOS device excellent, but it has 50MB memory limit which MacOS doesn't and can exceed it to show me full behaviour of xRay core like in android/windows. So it could be REALLY handy to be able to debug mac Designed for iPad since we support macOS on M chip and later and it works really well (except this debugging issue that customers dont know about).

Accepted Answer

This is a packet tunnel provider, right? If so, be warned about our advice in TN3120 Expected use cases for Network Extension packet tunnel providers.

Also, if you using Go, make sure you have a main executable UUID. Without that, you’ll likely encounter weird problems. See TN3178 Checking for and resolving build UUID problems.

Returning to your core problem, you could create a temporary macOS app with a macOS packet tunnel appex embedded within it. That’ll likely improve your debugging experience.

IMPORTANT macOS supports both appex and sysex packaging for packet tunnel providers. See TN3134 Network Extension provider deployment. Most folks use the sysex packaging on the Mac, but in this case you specifically want the appex packaging.

it has 50MB memory limit

I presume that you only bump into this limit with debug builds of your product? Because you’ll eventually need to deploy this product to iOS, and there’s no avoiding the limit then.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Debug Tunnel.appEx on mac Designed for iPad
 
 
Q