With iOS 27, Apple turned a long-standing warning into a hard rule: apps must adopt the UIScene lifecycle. For years iOS only logged a runtime warning when an app didn't. On iOS 27 an app that doesn't adopt scenes is stopped at launch.
For Adobe AIR apps this showed up as a crash right after start, EXC_BREAKPOINT on the main thread, with this in the backtrace:
UIKitCore _UIApplicationEvaluateRuntimeIssueForNoSceneLifecycleAdoption UIKitCore -[UIApplication workspace:didCreateScene:withTransitionContext:completion:]
We hit it in our own apps in September 2026: fine on iOS 26, dead on iOS 27, and an App Review rejection with exactly this trace.
The cause: a build-time gate
The important detail: iOS 27 enforces the scene rule only for apps built against the iOS 27 SDK. It reads the SDK version from two places:
- the
DTSDKName/DTPlatformVersionentries in the app'sInfo.plist, and - the
LC_BUILD_VERSIONload command of the main executable (sdk 27.x).
When ADT packages an IPA on a Mac with Xcode 27, both say "iOS 27", the gate fires, and an AIR runtime that isn't scene-aware crashes.
Just adding a UIApplicationSceneManifest to your InfoAdditions does not help with older AIR versions: the crash turns into a black screen, because that runtime never creates its window inside a scene.
What works
1. Use a current AIR SDK. AIR 51.4.1 moved the iOS runtime to a storyboard and the scene lifecycle and generates the scene entries in Info.plist itself. 51.4.1.2 and 51.5 fixed further iOS 27 scene issues. Stay current.
2. Stamp the SDK version down to 26.x – both halves. In our tests, with iOS 27 devices, iPads running iOS 17 and the iPad app on the Mac, the combination that reliably works is:
- in
adt.cfg:UseXcodeForIPAConstants=false, so ADT writes iOS 26.2 values intoInfo.plistinstead of reading Xcode's, - after packaging, set the main binary's SDK to 26.2 as well, keeping its minimum OS, then re-sign:
BIN=Payload/MyApp.app/MyApp
MINOS=$(vtool -show-build "$BIN" | awk '/minos/{print $2; exit}')
vtool -set-build-version ios "$MINOS" 26.2 -replace -output "$BIN.new" "$BIN" && mv "$BIN.new" "$BIN"
codesign -f -s "Apple Distribution: …" --entitlements entitlements.plist Payload/MyApp.app
SDK 26.2 still meets Apple's minimum-SDK rule for uploads.
3. Check every build before you upload.
vtool -show-build Payload/MyApp.app/MyApp | grep sdk # must say 26.x
Our App Review rejection came from exactly one build that skipped this step: Info.plist said 26.2, the binary said 27.1. Since then a script does it for every store build, and the check is part of the release list.
Also watch out for
- Debug and interpreter builds can trap on iOS 27 regardless. Test the store-signed build via TestFlight.
- The iOS 27 Simulator shows the same symptom: the app installs but never comes to the foreground. The same
vtoolstamp on the simulator binary fixes it. - iPads on iOS 17 need the opposite care: if an SDK like Firebase pulls in
SwiftUICoreas a hard dependency, the app won't start on iOS 17, where that framework doesn't exist. Weak-link it.
Why our extensions weren't the problem
The crash sits in AIR's app startup, not in any extension. But it's a good example of why we test every release on the newest iOS in our own published apps first: we saw the crash, the rejection and the fix in our own apps, early, and that experience goes straight into our extensions and our support.
Native extensions for Adobe AIR, tested on the current iOS, Android and macOS in our own apps: klughomesolutions.com
More articles
- Shipping an AIR app to the Mac App Store and TestFlight
- Why AIR native extensions don't need a package manager
- One app, many native extensions – and they have to work together
- Two-way voice with echo cancellation in Adobe AIR
- Camera and H.264 live streaming in Adobe AIR, without AIR's camera
- Sign in with Apple and Google in an Adobe AIR app
- A distriqt alternative for Adobe AIR native extensions