Workaround: MobileIron Tunnel vs. Xcode device debugging
Workaround: MobileIron Tunnel vs. Xcode device debugging
- Subject: Workaround: MobileIron Tunnel vs. Xcode device debugging
- From: Owen Hartnett <email@hidden>
- Date: Sun, 12 Jun 2016 19:41:40 -0400
Workaround: Apparently, MobileIron uses the app ID to lock down the tunnel VPN. Any app with that ID which doesn’t have the wrapper doesn’t get through the tunnel.
To workaround, create another target just for debugging on the device with a different App ID. Cumbersome, but at least you can now debug on the device.
-Owen
> On Jun 9, 2016, at 11:00 AM, Owen Hartnett <email@hidden> wrote:
>
> We've just switched to MobileIron here, using the per-app tunnel provided by MobileIron. We hand off IPA files to our IT (which controls the MobileIron) and they run it through MI system and publish it. MI wraps the app with some type of protection so that it can operate through their tunnel VPN. If I just try and compile the app in Xcode and run it on the device, the vpn refuses to work because the app was not delivered by the MDM server. Thus, I cannot debug with Xcode on the device. I can't even use xctest on a device.
>
> I know this is a question for MobileIron, but IT handles our MI account, and they say they'll request more information on this, but what I'm asking is if there are people here who use MobileIron's tunneling, and are able to debug on the device in Xcode. If I know it's possible, then I can leverage our IT guys to push for that solution.
>
> Thanks for any help,
>
> -Owen
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden