Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Well crap... beta 5 breaks enterprise secure containers. (Bug reported to Apple this morning.).
In the initial beta, I had to reset my corporate email app to reestablish the secure container. Not a big deal.
Since then, all updates went without a hitch. With beta 5, it broke the secure container again, only now it won't reset. Removing the app and policies and reloading no longer works.
 
  • Like
Reactions: NetMage
Well crap... beta 5 breaks enterprise secure containers. (Bug reported to Apple this morning.).
In the initial beta, I had to reset my corporate email app to reestablish the secure container. Not a big deal.
Since then, all updates went without a hitch. With beta 5, it broke the secure container again, only now it won't reset. Removing the app and policies and reloading no longer works.

I had a related issue. Turned out reloading the policy didn’t work because the server was trying to send me a Mac policy. I figured out that the issue is that safari reports as “desktop” safari, and the app that requests the policy creates a hidden WKWebView and sends the wrong information to the server.

I went into the safari app and set it to always load the server web page as a mobile app. Then I relaunch the provisioning app, and it sent the proper profile and all was finally well.
 
I had a related issue. Turned out reloading the policy didn’t work because the server was trying to send me a Mac policy. I figured out that the issue is that safari reports as “desktop” safari, and the app that requests the policy creates a hidden WKWebView and sends the wrong information to the server.

I went into the safari app and set it to always load the server web page as a mobile app. Then I relaunch the provisioning app, and it sent the proper profile and all was finally well.
That is a bummer. Fortunately my MDM profile does not have this issue. Seems that Safari “desktop view” will be ignored by many sites again once iOS 13 goes public.
 
  • Like
Reactions: rjohnstone
I had a related issue. Turned out reloading the policy didn’t work because the server was trying to send me a Mac policy. I figured out that the issue is that safari reports as “desktop” safari, and the app that requests the policy creates a hidden WKWebView and sends the wrong information to the server.

I went into the safari app and set it to always load the server web page as a mobile app. Then I relaunch the provisioning app, and it sent the proper profile and all was finally well.
Unfortunately this didn't fix the issue.
We use Blackberry Work for email and other secure, in house developed apps.
I can finally get through the provisioning process, and policies are downloaded. The app starts, authenticates and then immediately crashes.
Reading through the Beta 5 release notes now. I suspect the app may be using a deprecated UI call or function.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.