We used Xcode 26.2 to successfully build iOS 12 apps before March 25. After that, the same code crashes on iOS 12 at startup. It would be great if Apple officially confirms if it drops iOS 12 support in such a weird way, or if it was an issue that can be resolved.

The same situation with our app, crashes on iOS 12 on startup if the app was built and processed by TestFlight after March 25. More than 400 active users of iOS 12 won't get the update if the issue is not resolved :(

The same for Organic Maps: internal CI TestFlight build on March 25 works on iOS 12 device, the same binary with a few string resource changes, built on March 26 does not work. Built with the frozen version of Xcode 26.2. That implies some kind of Apple involvement when builds are uploaded.

I've reported it to the Apple in the Feedback Assistant as FB13728754. Does anyone have a small and simple project to reproduce the issue?

The workaround with changing the code in the main app does not help. Any changes in a statically linked library do not appear without a "Clean build folder" and then full rebuild. Any other workaround that works for you? It looks like a regression, did anyone report this bug to Apple's Xcode team?

Opening iOS Settings, and Developer Tools, resetting "Clear Trusted computers" and then authorizing the iPhone again helped in my case with XCode 15 and iOS 17.0.1

Hope it will be fixed, the same issue with broken TTS on the iOS 16 simulator.

Looks like this command before the build helps: sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService

Same problem with all Xcode 13 versions, including the latest 13.2.1 Any workarounds or hints?