Thanks for the clarification. However, this is quite concerning from a developer and user-impact perspective. This app version was: • successfully built and uploaded with Xcode 16.4 • accepted in App Review • distributed through the App Store Despite having a deployment target of iOS 12, the build is now crashing on launch for all iOS 12 users, without any prior warning during submission or review. As a result, a previously working user base on iOS 12 has effectively lost access to the app overnight after updating, which is a significant regression in functionality. If iOS 15 is now a strict requirement for App Store distribution, it would be much safer for developers if: • the upload was rejected at submission time, or • a clear warning was shown before release rather than allowing distribution of a build that cannot run on supported devices declared in the app’s deployment target. Is there any recommended way to: Restore functionality for existing iOS 12 users (e.g. keep last compatible version available), or Prevent this situation when submitting updates in the future? Appreciate your guidance.

I'm seeing exactly the same crash, same source code, same Xcode version two weeks ago did not have the issue. I've pushed a new build 2 days ago and users with iOS 12 are getting a crash on launch.

I'm seeing exactly the same issue. I've filled a radar (feedback/22395634)

Also interested in knowing if there's a solution for this. I'm facing the same issue with my App purposing old iPads to use them as Digital Photo Frames.