Problem Xcode 8, Swift 2.3 Archived version crashing when starting on iOS 9.2.1 & # 8594; IOS 9.0

Question

I upgraded my application from Swift 2.2 to Swift 2.3 with minimal changes using Xcode 8.0

Everything works fine from Xcode in debug or release configuration

When testing the exported archive on IOS 9.2.1 and lower devices (Adhoc or development preparation profile) I get a crash when

SpringBoard[54] <Warning>: BSXPCMessage received error for message: Connection invalid SpringBoard[54] <Warning>: BSXPCMessage received error for message: Connection invalid timed[58] <Notice>: (Note ) CoreTime: Current mcc: '0' simulated:'0'. SpringBoard[54] <Warning>: HW kbd: Failed to set (null) as keyboard focus <Error>: error evaluating process info - pid: 1038, puniqueid: 1038 (UIKitApplication:) <Notice>: Service exited due to signal: Segmentation fault: 11. 

This means that it is trying to access memory somewhere invalid.

I tried writing NSLog and tracing, but cannot find the point where it crashes.

I suspect this may be due to storyboard changes from Xcode 7-8.

I searched for this error for too long, because it takes me a lot of time, because I have to create an archive every time. 95% of the time when it crashes at startup, but sometimes I manage to start it.

I had no problems running on devices with iOS 9.3 or iOS 10

----- Update ----

I downloaded Xcode beta 8-1 and this also fixes my problem.

So either use Xcode 7.3 or 8.1 beta +, but not 8.0. I looked at beta 8.1 releases, but did not mention this issue.

----- Update ----

HatTip to @KoCMoHaBTa when upgrading to version 8.1, this problem will be fixed if you also do not change the deployment target to 9.0, after which it will be re-executed.

Answer 1

Perhaps I was a little late for the party, but we have been studying this error for 2 days. The following postoverflow post fixed this for us: Xcode 8 build error on iOS 9.2 and below

It also explains that in iOS 9.3 it is so different from the fact that setting the iOS version as the deployment target fixes all the problems “magically”

Maybe worth checking out :)

Answer 2

In the end, for an unknown reason, random crashes started to appear again, even if we set the deployment target to 8.4.

So, in the end, we finished creating the deployment target for iOS 9.3, which eliminates the use of the application in the affected version.

Unfortunately, at the moment we could not afford to switch to fast 3, so this could also be an option.