Posts

Post not yet marked as solved
8 Replies
I am still consistently seeing this issue when I try to drag and drop a .cer file onto my simulators per the instructions in https://developer.apple.com/library/archive/qa/qa1948/_index.html. However, if I put my .cer file on a webserver an navigate to it using safari in the simulator, the profile installation process happens as expected.The drag and drop method tries to open the .cer file using the file:// scheme. The iOS 13 release notes do not specifically mention that loading a .cer file using the file:// scheme has been dropped, but they do mention changes to what file:// urls can do.https://developer.apple.com/documentation/ios_ipados_release_notes/ios_13_release_notes?preferredLanguage=occ"Removed support for FTP and File URL schemes for Proxy Automatic Configuration (PAC). HTTP and HTTPS are the only supported URL schemes for PAC. This affects all PAC configurations including, but not limited to, configurations set using Settings, System Preferences, Profiles, and NSURLSession APIs such as connectionProxyDictionaryand CFNetworkExecuteProxyAutoConfigurationURL. (28578280)"PAC isn't directly related to ca certs but perhaps this bug was introduced with those changes.
Post not yet marked as solved
1 Replies
Through some experimentation I have found that I can log in to the account on the server running the XCode bots, start XCode and launch the simulator. Then I can start each and every simulator I want to test with and install my root certificate. And then the next time and XCode iOS upgrade comes out I can do it all over again. It seems like I've missed some critical step here. Is anyone else testing iOS app code against test servers with self-signed certs?