iOS 14.2 app crashes in arm64e devices if deployed via MDM

App & System Services Core OS
MViquar OP
Created Nov ’20
Replies 55
Boosts 0
Views 13k
Participants 49
iOS 14.2 applications developed using Xamarin are crashing in arm64e CPU devices. These Xamarin apps are deployed using a Mobile Device Management tool(Airwatch or Microsoft Intune). However, the same iOS apps work fine in iOS 14.2 when it is installed via the App Store.

We have seen this issue in Xamarin iOS apps like-
Microsoft Azure
Microsoft Seeing AI, etc.

Steps to reproduce,

  1. Configure an MDM tool

  2. Deploy a Xamarin based iOS app to arm64e device (like iPhone 11)

  3. Launch the app after installation

Expected result:
The app should launch and work as expected

Actual result:
The app crashes after 20 seconds with the following error -
Exception Type: EXCBADACCESS (SIGKILL)
Exception Subtype: UNKNOWN0x32 at 0x0000000106464018
VM Region Info: 0x106464018 is in 0x106464000-0x106468000; bytes after start: 24 bytes before end: 16359
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
VMALLOCATE 106460000-106464000 [ 16K] rw-/rwx SM=PRV

  • --> mapped file 106464000-106468000 [ 16K] r-x/r-x SM=COW ...tid=969d6cc3

VMALLOCATE 106468000-1064e8000 [ 512K] rw-/rwx SM=PRV

Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:process-launch watchdog transgression: application<com.microsoft.azure>:1696 exhausted real (wall clock) time allowance of 20.00 seconds | ProcessVisibility: Foreground | ProcessState: Running | WatchdogEvent: process-launch | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 24.050 (user 24.050, system 0.000), 20% CPU", | "Elapsed application CPU time (seconds): 20.001, 17% CPU" | ) reportType:CrashLog maxTerminationResistance:Interactive>
Triggered by Thread: 0

Thread 0 name: tid_407 Dispatch queue: com.apple.main-thread

Replies  55
Boosts  0
Views  13k
Participants  49
ny21david OP
Nov ’20
We have several thousand enterprise users who use a variety of MDM packages, including MobileIron, IBM MaaS360, Apple Configurator, AirWatch, and Microsoft Intune. ALL of them are experiencing this crash of our Xamarin.iOS app if the device is running iOS 14.2.
3
6RiL OP
Nov ’20
This bug is also extremely critical from my side.
Now more than 4000 devices (iPhone 11 and XR) at one of my customers, who uses Intune to deploy his Xamarin IOS custom app, are affected by this problem.
I also reroduced this issue.
I have referenced my public store apps and ABM custom apps (same Xamarin IOS core as public app) in my Intune portal.
I have successfully deployed these applications on 13.x and 14.1 devices.
I then migrated the devices to 14.2 and reproduced the problem: The splash screen is displayed for a few seconds, then the application dies.
Iphones 7,8 & X are not affected. I reproduced on 11 and XR.
NOTE : deploying an IPA works properly
2
jjs7one OP
Nov ’20
We are experiencing the same thing with our MDM and an app we use. Has anyone found a solve?
2
Optikam OP
Nov ’20
We are experiencing the same issue. We can confirm that the issue occurs when deploying a Xamarin.iOS AppStore app via MDM to an arm64e device running iOS 14.2.

Tested devices that are affected:
iPad Pro 11" 2nd gen
iPad Pro 12.9" 3rd gen
iPad 8th gen

Tested devices that are not affected:
iPad 5th gen

0
gfdfgdfgdfgdgf OP
Nov ’20
Same issue here many users are impacted.
0
namadori OP
Nov ’20
Same here, about 100 corporate iPads managed with Intune cannot use our custom Workforce Management app anymore. This is really impacting us badly.

Please share any workaround that will be available.
0
CRocksmith OP
Nov ’20
Hello all,
We are also in the same position. Unfortunately our application is used by COVID testing sites across the United States, this problem has caused massive headaches for their front line staff.

Please look at this as a priority.

Thank you
2
progrob OP
Nov ’20
We are experiencing this same issue with several users distributing the Field Service Mobile (Xamarin) app using Microsoft Intune. We are at about 50% success rate with iOS 14.2.
0
phalder OP
Nov ’20
We have several users facing this issue and its impacting our Business.
0
tomappletom OP
Nov ’20
We are experiencing the same crash with our MDM package, MobileIron.
0
reshma90 OP
Nov ’20
Even we are facing the same Issue with Microsoft Intune
0
matthiasfromkarlsbadsd OP
Nov ’20
This bug is extremely critical for us as well. Several customers reported this problem for different MDM-Systems like MobileIron and Baramundi.
0
reknab.velsol OP
Nov ’20
If your app is published as a Custom App (as most of ours are) and therefore not visible on the App Store, using redemption codes from Apple Business Manager (versus relying on Managed Licenses) also allows the app to launch. This may be a temporary option for business users that have already upgraded to iOS 14.2 and cannot launch apps distributed via MDM using Managed Licenses. Obviously with a large number of users this may be prohibitive, but with a relatively small number of users sending them redemption codes may be an option.
0
tkarnatz OP
Nov ’20
We also are experiencing the same issue with our healthcare apps. A variety of MDMs, the same app was functioning properly through the MDMs on previous iOS versions and continues to function in iOS 14.2 when loaded through the App Store.
0
dedata OP
Nov ’20
This is so frustrating. This is affecting all our customers that deploy our iOS app via IBM MaaS360 to arm64e devices running iOS 14.2
1
simbel OP
Nov ’20
It could be interesting to try and find if we have more in common than MDM, iOS 14.2, new devices and Xamarin. When I look at my crash logs, it seems to be pointing to Firebase ->

Binary Images:
0x100818000 - 0x104313fff <APPNAME> arm64 <3126bb8e603136a4a13b2c6c62e6500e> /var/containers/Bundle/Application/<UUID>/<APPNAME>.app/<APPNAME>
0x104854000 - 0x10488bfff FirebaseMessaging arm64 <d70a4d9b0fd23dc9854372da0d304cf2> /var/containers/Bundle/Application/<UUID>/<APPNAME>.app/Frameworks/FirebaseMessaging.framework/FirebaseMessaging
0x1048b4000 - 0x1048c7fff FirebaseCore arm64 <a986f726bd943fb29b706326b0fd20f4> /var/containers/Bundle/Application/<UUID>/<APPNAME>.app/Frameworks/FirebaseCore.framework/FirebaseCore

Firebase is a commonly used service, it wouldn't be surprising if all our solutions are using it.
0
YYHYH OP
Nov ’20
Any workaround ?
0
mistersee OP
Nov ’20
Also a major issue for our app. Seems to be only for apps deployed via MDM on ARM64 with iOS 14.2.

1,000s of affected users for a life critical application (health).
1
Optikam OP
Nov ’20
I think these are the commonalities:

OS: iOS 14.2, iOS 14.3 Beta 1, iOS 14.3 Beta 2
Apps: Any Xamarin.iOS app (even apps that don't use any external dll/nuget libraries crash)
Hardware: Any arm64e cpu device (ex: iPad Pro 11" 1st/2nd gen, iPad Pro 12.9" 3rd/4th gen, iPad 8th gen, iPad Air 3rd/4th gen, iPhone 11, etc)
Deployment: Deployed via any MDM or the Apple Configurator 2 from an App Store source (Ad-hoc .ipa deployment works fine even via MDM or Apple Configurator 2, direct Apple Store app install works fine)

1
Bharat_Kolla011 OP
Nov ’20
Same issue, all our users using MDM are effected. Devices running iOS 14.2 are not loading our app
0
OP
Apple
Nov ’20
Thank you all for these reports. We are investigating this, and can use your help with the investigation.

To start, please file a bug report detailing your setup, including whether your app was built using "native" Xcode or using a third-party environment (such as Xamarin, as noted in a few of your reports), what device(s) you're using, and what mechanism you're using to install the app (if using MDM, which provider?).

Additionally, to help determine possible culprits, please perform the following steps, and include the results in your bug report.

First, create either an Enterprise, Development, or Ad Hoc-distributed build, and for the distribution options, enable the App Thinning and Rebuild from Bitcode options.

(Distributing Your App for Beta Testing and Releases describes this process.)

Next, use Configurator 2 and load the app, with the MDM profile, onto the targeted device. Run the app and note in your bug report if this results in a working app or not.

Please include the following in your report:

  • Symbolicated crash logs.

  • Logs that you have gathered from the console when the hang took place.

  • Sysdiagnose [1] on the device after the hang took place.

  • The time and date you performed these steps.

Once you file your bug report, please add your FB number to this thread so we can track them.

Thanks for your help tracking this down,

—jasonag.


[1] To create an iOS sysdiagnose, perform the following steps:

  1. On the device after you have reproduced the issue, hit the up and down volume buttons at the same time. You will notice a slight vibration. Note the time you do this.

  2. Wait about 5-10 minutes, and navigate to Settings -> Privacy -> Analytics & Improvements.

  3. Scroll down to the bottom of the list and find the entry for sysdiagnose_todays_date.

  4. Select this file and Air Drop it to a computer.

  5. Zip the sysdiagnose_todays_date file and upload it to the bug report.

  6. Note the time from Step 1 in your bug report.


1
SKoivisto OP
Nov ’20
Hi all,

we are also experiencing this issue. Please prioritise this issue.
0
efb-admin OP
Nov ’20
This issue is affecting our airline and we have pilots that cannot open a couple of crucial apps because of this. I hope there is a solution very soon! 🤞
1
reknab.velsol OP
Nov ’20
Submitted FB8907917 with symbolicated crash log, sysdiagnose and other info requested by Jason @ Apple below.

https://feedbackassistant.apple.com/feedback/8907917
0
ramit_123214 OP
Nov ’20
Submitted FB8914570 for this issue with the required information as requested by jasonag in this thread.
https://feedbackassistant.apple.com/feedback/8914570
0
iOS 14.2 app crashes in arm64e devices if deployed via MDM
First post date Last post date
 
 
Q