@qpwr See this method to make builds unavailable: https://developer.apple.com/help/app-store-connect/manage-your-apps-availability/make-a-version-unavailable-for-download First I am uploading a new build with target iOS 15. In my case this is app 2.15.2. This will prevent iOS 12 users from getting that version or future versions (end of the road for them!). Second, I will make 2.15.1 unavailable using the function above (this build is broken for iOS 12 users due to the bootstrap problem this thread is about). iOS 12 users can then make a fresh install of 2.15 which is the last known version to work for them. Note that I cannot just make the current App Store version unavailable, the availability method does not let me do that (I can untick the box but the save button doesn’t save it). I can only make earlier versions unavailable. Therefore I first have to upload a new version (2.15.2 in my case). Edit: Now that Apple have fixed the issue I can upload a new build for iOS 12. Too bad, have spent half the night to add UIScene support.

@ChristianBr you might be interested in these related posts: https://developer.apple.com/forums/thread/821338 https://developer.apple.com/forums/thread/821370

@Manuel_Apps I am in the same situation... the current version of my app on the App Store is defunct for iOS 12 people. I am now working on a build with target iOS 15. As soon as it’s submitted and released I am planning on making the broken release unavailable. This way iOS 12 users have to uninstall the broken version so they can reinstall the (still working) version before that. I totally agree with you. I wish Xcode 16 (the first Xcode that did not support iOS 12 anymore) would have prevented me from building the app with the unsupported target. Instead it was waved through without warning. Yes, the Xcode support page said it didn’t support iOS 12, yet there was no hard stop. I was not aware I was sitting on a time bomb for at least 1 year. I thought only debugging was not supported but building was -- because it worked. The broken app happened a few days ago when my customer was holding an event in front of an audience, some of which had iOS 12 on their iPads. One can imagine they were not happy when the new release did not work. FWIW here’s my post with the same story

Thanks @Manuel_Apps and @BioDranik for your metoo’s. In the meantime I have received a response from dev support. They gave me the same answer that is found in the thread pointed to by @DTS Engineer . This is the tech part of the answer: When you submit to the App Store, Apple modifies your binary. They strip your signature, encrypt the binary and re-sign it. This encryption alters the Mach-O file's page alignments and load commands. Nothing I can do about that. I’m fine with progress but I wish Xcode would have somehow prevented me from using the unsupported deployment target. Ever since Xcode 16 (which also does not support iOS 12) I thought my target was ok. So I will bump the target to iOS 15 (for now, in the future possibly higher). Since my app in the App Store is defunct for iOS 12 users I will upload a build with target iOS 15 and then mark the broken build as unavailable (App Connect > Pricing and Availability). This way the legacy users will get the last working version.

Addendum: I’ve created a simple minimal UIKit app that produces the same bootstrap error on the iPhone 5s with iOS 12.5.8. Launch storyboard shows, then suddenly disappears. The project is configured for automatically managed signing. My provisioning team profile expires in 11 months, my dev certificate in Oct 2026, and all other items in the details have checkmarks.

I’ve managed to run the Xcode 26.4 debugger with an app on an old iPhone 5s running 12.5.8 (though it failed for a different reason). The trick was to install a developer disk image for iOS 12.4. Since Xcode does not grab it from the old iPhone I found it on GitHub where someone collected these old images. You need to copy the dmg and signature to /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport . Good luck.

Thank you for your post. If I’m not mistaken this means that at the time when Xcode 27 becomes mandatory, the app’s deployment target must be iOS 13 or higher since the UIScene class and Info.plist keys are iOS 13.

I'm a freelancer in iOS development but every now and then I get a request to make small websites for distant relatives or friends or acquaintances of them. I don't like those heavy weight websites that take ages to load (hello WIX) with tons of js and those damned cookies. On the other hand I don't like to make static websites myself in html like in the 90s which look super sparse (though they load very fast). What I would really like is to make use of my Swift/SwiftUI knowledge in web. Been thinking about some minimal framework or some kind of method to do that. Found some toy projects but I don't want to bring the iOS L&F to the web, I want websites to look like websites but made with SwiftUI. No more CSS and HTML. Compiling SwiftUI to html is the first naive idea that comes to mind. But I lack the broad knowledge of web technologies out there so I find myself unable to devise anything that could nearly rival other sophisticated frameworks.

Have this too, I hope Apple can fix this server-side and whitelist Xcode 15.0.1 being a production version. I downloaded it directly from developer.apple.com, not from the App Store app.

+1 Waiting for Xcode 14 update. Hope it'll come soon because I need to test the app on a real device before uploading for customer.

I am having the same problem with 404 and 1404 error codes. Sorry that I am of no help. The API documentation of NSBundleResourceRequest says "This class ignores calls from Mac apps built with Mac Catalyst." and I am wondering if this is also true for M1 apps designed for iPad.

I have the same issue like the OP, and it still exists in iOS 16 beta 2, whether I use NavigationSplitView or NavigationView with column-style. Are there no other view modifiers that are called? I have a singleton audio engine in the app, and the detail view initializes itself on the engine at .onAppear. Can't have a new audio engine for each detail view, especially if the previous detail view is not discarded.

Ok I'll answer my post myself: I have written my own audio "engine". It runs in my own effect plugin. In the render callback I can do whatever I want with the input channels. This means I have to invoke render callbacks of all generators and effects myself, and I have to mix buffers myself, Accelerate framework to the rescue.

Hi, I have the same issue, did you or Apple find a solution to this?