We have an office application used internally within our enterprise. The Provisioning Profiles (PP) for the app were about to expire, so we updated the PP and released a new version. However, we've encountered an issue where some users did not update their phones in time. After the app expired, they found it unusable and downloaded the new version, but the newly downloaded app also crashes on launch. Restarting the phone does not resolve the issue, and this primarily occurs on iOS 18.3.2. What could be the cause of this problem, and how should we address it?
Enterprise App Crashes on Launch on iOS 18.3.2
I've recently been looking into some issues which might be related to what you describe. Can you open a bug report? We need a sysdiagnose from a device experiencing the crash attached to the bug report so we can investigate. Once you create the bug report with the sysdiagnose attached, please post the FB number here for my reference.
— Ed Ford, DTS Engineer
I have the same symptoms. In my case, I turned on developer mode to check the status, and I connected the iPhone to the Mac, and the crash is resolved. (If I turn off developer mode again, the crash will occur.)
@ileok, what's the FB number for your bug report?
— Ed Ford, DTS Engineer
FB Number is FB17157281.
thank you.
@ileok any update on this issue?
@ileok, thanks for fililng FB17157281. There's something in your logs that I haven't seen before when looking in to these, so I'd like to get a clarification from you — is only your app affected, or are you seeing apps from other companies affected as well?
— Ed Ford, DTS Engineer
@DTS Engineer We have about six corporate apps. Different employees have different cases of problems. App A crashes, B not crashes, and other employees crash only B apps. Another employee crashes both A and B apps. The difference is that the non-collisioning app is that the new version was overwritten with the existing app installed, and the conflict is when the app was newly reinstalled. (Not sure)
We had some similar issues with our enterprise builds.
The following solved it for us:
- Use Configurator to remove the enterprise profiles
- Delete the app
- Reboot the device
- Reinstall the app and profile
We believe this is addressed in iOS 18.5 beta 3. Here is the release note:
Security
Resolved Issues
Fixed: Some enterprise apps might not launch. If you experienced this issue on iOS 18 or later, uninstall all enterprise apps from the device and reinstall them.
If you test on iOS 18.5 beta 3, and still find that your apps can’t launch after following those instructions, please file a bug report with a sysdiagnose attached. Once the report is filed, please post the FB number here so that I can follow-up on it.
— Ed Ford, DTS Engineer
It still crashes after iOS 18.5 beta3 update. FB number is FB17331162.
@ileok, thank you for FB17331162. Just to confirm a detail before we dive in and look at this further, you removed all of your enterprise apps from the device and then reinstalled them?
— Ed Ford, DTS Engineer
Yes, I deleted (and removed the profile) all enterprise apps and then reinstalled (and installed the profile).
@ileok, we've had time to analyze this further, and your sysdiagnose contains a crash report with the following (edited here for privacy and clarity):
Termination Reason: Namespace DYLD, Code 1, Library missing
Library not loaded: @rpath/Base64.framework/Base64
[...]
Reason: tried: [...]/YourApp.app/Frameworks/Base64.framework/Base64' (code signature invalid
This framework is not correctly signed, it is signed for development, but not for a distributed app. This isn't related to the issue we resolved in iOS 18.5 beta 3, and is one that you can address for your app by fixing up its signing for distribution.
I'd like to keep this thread focused on the issue we resolved in iOS 18.5 beta 3, so if you need any further help updating your code signing to address that error, I suggest you start a new thread focused on that issue.
— Ed Ford, DTS Engineer