After upgrading to Xcode 7.3 we now receive the following message when building
Cannot create __weak reference in file using manual reference counting
Thankfully we can get around this via the projects build settings.
Set: Build Settings > Apple LLVM 7.1 – Language – Objective C > Weak References in Manual Retain Release to YES.
While attempting to update an iOS application with a new provisioning profile for AD-HOC distribution I ran into this error while performing the export step after archiving:
Missing iOS Distribution signing identity for …
Recently after our yearly provisioning profile updates we do for a client I wanted to run a quick debug version on a iDevice to make sure everything was still functioning. I connected the device and pushed the App to the device via Xcode. The device started up the App but Xcode returned:
Failed to get the task for process
The App continued to run on the device I just couldn’t hit any breakpoints as I used the App on the device. A quick search turned up something interesting, it seems in my haste I had assigned my newly renewed Ad-Hoc profile to my debug build settings. After changing the debug profile to use my Development certificate everything was working fine again.
Source: Stack Overflow
A new version of iOS always brings new changes. This one was encountered while doing our yearly Ad-Hoc Distribution Profile renewal. An App that hasn’t been changed in a while suddenly no longer wants to make web requests. Nothing is seen on the iDevice except for a blank table. Debugging in XCode we get the following error message:
The resource could not be loaded because the App Transport Security policy requires the use of a secure connection
The permenant fix is to add an SSL certificate to your HTTP endpoint and make sure all requests are HTTPS but this being a client environment I couldn’t wait for them to do so and just needed to implement the work-around as follows:
[ProjectName]-info.plist fileNSAppTransportSecurity as a DictionaryNSAllowsArbitraryLoads as Boolean and set its value to YES (see image below)
Now just build and you are set!
Note: this is a blanket exemption but you can also further configure as mentioned here (How do I load an HTTP URL with App Transport Security enabled in iOS 9?)