Environment
Devices: e.g., iPhone 12 mini, iPhone 16 (multiple units)
OS: iOS 26 beta 2 and beta 4 (23A5297m)
Distribution: Apple Enterprise Program (In-House), deployed via MDM InstallApplication
Tooling: Xcode (latest available for iOS 26 betas)
Summary
Apps signed for Enterprise (In-House) distribution install successfully on iOS 26 betas via MDM, but terminate immediately on launch. The same builds run if installed from Xcode on the same devices. This is a regression from pre-iOS 26 versions where Enterprise builds installed via MDM launched normally.
Steps to Reproduce
Archive an iOS app and export for Enterprise (In-House) distribution.
Deploy the .ipa via MDM using InstallApplication to a device on iOS 26 beta (e.g., 23A5297m).
Tap the app icon to launch.
Actual Result
The app quits instantly on launch. System logs show launchd/runningboard errors, including NSPOSIXErrorDomain Code=85 (“Bad executable (or shared library)”):
runningboardd(RunningBoard)[34]: Process start failed with Error Domain=NSPOSIXErrorDomain Code=85 "Bad executable (or shared library)" UserInfo={NSLocalizedDescription=Launchd job spawn failed}
runningboardd(RunningBoard)[34]: Launch failed with Error Domain=NSPOSIXErrorDomain Code=85 "Bad executable (or shared library)"
SpringBoard(FrontBoard)[35]: Bootstrapping failed ... NSUnderlyingError = { NSLocalizedDescription = Launchd job spawn failed; }
Expected Result
Enterprise-signed builds installed via MDM should launch as they did on iOS 25.x and earlier.
Regression?
Works on iOS versions prior to 26.
Works on iOS 26 betas when installed from Xcode (developer-signed run).
Fails only for Enterprise (In-House) builds delivered via MDM.
Additional Notes / Possibly Related
We also reproduced a similar failure mode with a minimal Safari Web Extension project: it installs and appears under Settings → Safari → Extensions, but enabling it and opening Safari produces: “ is no longer available.”
Building a fresh project with a new bundle ID shows the same behavior on iOS 26 beta (23A5297m).
Logs contain: Error occurred during transaction: The provided identifier "" is invalid.
Running from Xcode (debug build) works.
Workarounds
None identified for Enterprise/MDM distribution. Only Xcode-installed builds run.
Impact
Blocks Enterprise deployment to our fleet on iOS 26 betas.
Feedback / Attachments
Included: sysdiagnose from an affected device, minimal Xcode project demonstrating the issue, Enterprise-exported app, and reproduction notes.
Happy to share additional logs or perform targeted tests if needed.
Request
Can Apple confirm whether this is a known regression vs. a policy/validation change in iOS 26 for Enterprise/MDM installs? Any guidance on a short-term mitigation or build/signing change we can apply would be appreciated.
Topic:
Business & Education
SubTopic:
Device Management