Xcode 14.3: App built is not able to open on iOS 13.6

And by the way, this list on 14.3 is not showing enough simulators.

You can create more simulators yourself. Click Manage Run Destinations at the bottom of that list, then switch to the Simulators tab and hit the + button at the bottom. It looks like the oldest simulator supported is iOS 13.7, but this may be sufficient to reproduce the problem.

BTW, the App Store usage chart shows very few people are still on iOS 13. And as you can see it’s a pain to support such old versions. Just something to think about.

Xcode 14.2

Same issue here.

same issue here.

iOS 13.6 ~ 13.7

Same issue for 13.3.1, it's most likely a problem for all iOS 13 versions. It's amazing how such a big company can have such bad backwards compatibility.

As for iOS 13 support, also consider this: all devices that can run iOS 13 can also run iOS 14 and even iOS 15.

So if you are not also supporting iOS 12 or earlier, then there’s no good reason to set your minimum target platform to 13 or 14. Anybody with an iOS 13-compatible device should be running iOS 15 or higher.

I have the same problem

Same issue here.

Termination Description: DYLD, Assertion failed: (gotLocation), function applyFixupsToImage_block_invoke_3, file /Library/Caches/com.apple.xbs/Sources/dyld/dyld-750.4.2/dyld3/Loading.cpp, line 779.

https://opensource.apple.com/source/dyld/dyld-750.5/dyld3/Loading.cpp

Search for fixupObjCStableSwift.

same

iOS 13

一直报错 Xcode 14.3 下 iOS 13.3.1 - 13.6

Incident Identifier: 6B7B0FB8-7EBA-43B8-A91E-F31CA3F565AF CrashReporter Key: 5cc0d14db3c3a6974c8d9ff7f4052259e46a4265 Hardware Model: iPhone9,1 Process: 111111 [925] Path: /Volumes/VOLUME/*/1111.app/111111 Identifier: com.11111.jht Version: 1.0.1 (1) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.11111.jht [1169]

Date/Time: 2023-04-18 16:21:35.2726 +0800 Launch Time: 2023-04-18 16:21:35.1288 +0800 OS Version: iPhone OS 13.6 (17G68) Release Type: User Baseband Version: 7.70.01 Report Version: 104

Exception Type: EXC_CRASH (SIGABRT) Exception Note: EXC_CORPSE_NOTIFY Termination Reason: DYLD 9 Assertion failed: (gotLocation), function applyFixupsToImage_block_invoke_3, file /Library/Caches/com.apple.xbs/Sources/dyld/dyld-750.4.2/dyld3/Loading.cpp, line 779.

Highlighted by Thread: 0

Backtrace not available

No thread state (register information) available

Binary Images: Binary images description not available

Error Formulating Crash Report: Failed to create CSSymbolicatorRef - corpse still valid ¯_(ツ)_/¯

EOF

I have the same issue !!!

Not all app crash. There are 2 in my hand, one is launched and the other crash always. iOS 13.6 iph.

Don't upgrade to xcode 14.3, unless your app need just work on iOS above 13.0 version, if you have upgraded, delete it and download xcode 14.2 from 'https://developer.apple.com/download/all/'.

Such problems have occurred on several of my devices, and user feedback has been received. After the problems, I chose Decisive Xcode to downgrade to 14.2 and submit again for AppStore review. It is recommended that you do not try to update Xcode when it is not stable.

And backward compatibility is a painful thing, according App Store using charts to see using iOS13 users percentage did little, but can't afford to choose compatible

Same issue

My users on iOS 13 are reporting crash on start as well. iOS 13.6 so far. Hope that Apple comes with more than suggesting them upgrading to iOS 15/16.

same issue

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0×0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Description: DYLD, Assertion failed: (gotLocation), function applyFixupsTolmage_block_invoke_3, file /BuildRoot/Library/Caches/ com.apple.xbs/Sources/dyld/dyld-733.3.1/dyld3/Loading.cpp, line 779. Highlighted by Thread: O

I have the same issue !!!

We've received several Feedback Reports on this crash, and are investigating. Thank you to those that filed those reports.

This is happening for us as well, would love to hear if this can be addressed in a future Xcode release.

Same for me...

We have to use Xcode 14.2 to fix this. Thanks Apple to fix this... 🙏😭

Any solution? or we should turn to xcode14.2?

Xcode 14.3.1 addresses this issue, and a RC version is available for download today.

14.3.1 same issue