Forum Xamarin.Forms

iOS 14.2 App Crashes if deployed via MDM, but not from Appstore

One of our customers uses an MDM to deploy our app to their devices. They get the app via Apples Volume Purchase Program and deploy the store version to their MDM. Since updating to iOS14.2 the app crashes on startup. On phones with iOS14.1 or lower the app launches just fine. We also have no issues when the app is installed directly through the app store.

How can i resolve this issue?

The crashlog doesn't give me much insight either:

Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:process-launch watchdog transgression: application<de.connect2mobile.bau-mobil>:2018 exhausted real (wall clock) time allowance of 20.00 seconds | ProcessVisibility: Background | ProcessState: Running | WatchdogEvent: process-launch | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 35.500 (user 35.500, system 0.000), 30% CPU", | "Elapsed application CPU time (seconds): 19.821, 17% CPU" | ) reportType:CrashLog maxTerminationResistance:Interactive>
Triggered by Thread: 0

Thread 0 name: tid_407 Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? 0x0000000106120018 0 + 4396810264
1 bau_mobil_ios.iOS 0x0000000105898548 mono_jit_runtime_invoke + 45811016 (mini-runtime.c:3165)
2 bau_mobil_ios.iOS 0x0000000105955518 mono_runtime_try_invoke + 46585112 (object.c:3161)
3 bau_mobil_ios.iOS 0x00000001059541e8 mono_runtime_class_init_full + 46580200 (object.c:552)
4 bau_mobil_ios.iOS 0x000000010586b89c init_method + 45627548 (aot-runtime.c:4712)
5 bau_mobil_ios.iOS 0x000000010587eec4 mini_llvm_init_method + 45706948 (llvmonly-runtime.c:797)
6 bau_mobil_ios.iOS 0x000000010311f5b4 mono_aot_mscorlib_init_method + 64
7 bau_mobil_ios.iOS 0x0000000105898548 mono_jit_runtime_invoke + 45811016 (mini-runtime.c:3165)
8 bau_mobil_ios.iOS 0x0000000105953bfc mono_runtime_invoke_checked + 46578684 (object.c:3220)
9 bau_mobil_ios.iOS 0x00000001058ef670 create_exception_two_strings + 46167664 (exception.c:207)
10 bau_mobil_ios.iOS 0x00000001058ef4cc mono_exception_from_name_two_strings_checked + 46167244 (exception.c:266)
11 bau_mobil_ios.iOS 0x00000001058bfbc8 create_domain_objects + 45972424 (appdomain.c:247)
12 bau_mobil_ios.iOS 0x00000001058bf208 mono_runtime_init_checked + 45969928 (appdomain.c:354)
13 bau_mobil_ios.iOS 0x0000000105897dd8 mini_init + 45809112 (mini-runtime.c:4391)
14 bau_mobil_ios.iOS 0x0000000105879d4c mono_jit_init_version + 45686092 (driver.c:2875)
15 bau_mobil_ios.iOS 0x0000000105a339d8 xamarin_main + 47495640 (monotouch-main.m:428)
16 bau_mobil_ios.iOS 0x0000000102f9d6d8 main + 2840280 (main.m:172)
17 libdyld.dylib 0x00000001a62056c0 0x1a6204000 + 5824

Thread 1:
0 libsystem_pthread.dylib 0x00000001efa6b754 0x1efa61000 + 42836

Thread 2 name: SGen worker
Thread 2:
0 libsystem_kernel.dylib 0x00000001d35491ac 0x1d3521000 + 164268
1 libsystem_pthread.dylib 0x00000001efa66458 0x1efa61000 + 21592
2 bau_mobil_ios.iOS 0x00000001059f6fb8 thread_func + 47247288 (sgen-thread-pool.c:196)
3 libsystem_pthread.dylib 0x00000001efa62b40 0x1efa61000 + 6976
4 libsystem_pthread.dylib 0x00000001efa6b768 0x1efa61000 + 42856

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000125810628 x1: 0x0000000000000010 x2: 0x0000000105b3a051 x3: 0x0000000000000000
x4: 0x000000016d1161a0 x5: 0x000000016d116098 x6: 0x000000000000002d x7: 0x0000000000000000
x8: 0x0000000000000001 x9: 0x000000012580b800 x10: 0x0000000000000007 x11: 0x0000000000000007
x12: 0x00000000fffffffd x13: 0x0000010000000000 x14: 0x0000000000000000 x15: 0x0000000000000000
x16: 0x0000000106120018 x17: 0x0000000000000001 x18: 0x0000000000000000 x19: 0x0000000105d7d170
x20: 0x000000016d116950 x21: 0x000000016d1167e8 x22: 0x0000000124a05760 x23: 0x000000016d1164e0
x24: 0x000000016d116590 x25: 0x000000012501ed00 x26: 0x0000000280f59bd0 x27: 0x0000000105d67000
x28: 0x000000016d1167e8 fp: 0x000000016d116460 lr: 0x00000001031ac4b4
sp: 0x000000016d116440 pc: 0x0000000106120018 cpsr: 0x80000000
esr: 0x8200000f (Instruction Abort) Permission fault

Answers

  • SimonPotter.0360SimonPotter.0360 USUniversity

    We are seeing the same issue with a small update.

    Xamarin apps deployed to iOS 14.1 with MDM configuration works
    Xamarin apps deployed to iOS 14.2 with MDM configuration fails to launch
    Xamarin apps deployed to iOS 14.2 without MDM configuration works

  • tkarnatztkarnatz Member

    We have the same with our customers. But, we have installed SimpleMDM in hopes of reproducing the issue in house and the apps run fine when distributed through that MDM.

  • MartinScdMartinScd USMember

    Same Here:
    AppStore Version deployed with MDM on iOS 14.2 Devices:
    Works on older devices like iPad Air2.
    On newer devices like iPad Pro 11" (1st Gen) crashes.

    If we create the ipa with a AdHoc Bundle Signing and deploy it on the iPad Pro 11" with MDM, it is working.
    Only the AppStore version deployed with MDM is crashing.

  • We have the same problem with JAMF MDM.

    I can confirm crashes on:

    • iPhone 11
    • iPhone SE 2. Gen

    It works fine on:

    • iPad Air 2
  • IainSmithIainSmith GBUniversity ✭✭

    We are getting the same issue too on:
    iOS 14.2 - iPhone 11 through MDM

    And totally fine on iOS 14.1 - iPhone 11 also I have almost exactly the same crash report too:

    Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:process-launch watchdog transgression: application<REDACTED>:441 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): 29.110 (user 29.110, system 0.000), 24% CPU", | "Elapsed application CPU time (seconds): 19.906, 17% CPU" | ) reportType:CrashLog maxTerminationResistance:Interactive>
    

    Once symbolicated and redacted project name the stack trace looks like:

    0x00000001031448a8                                                               (in REDACTED.Mobile.iOS)
    wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr (in REDACTED.Mobile.iOS) + 260
    mono_jit_runtime_invoke                                                          (in REDACTED.Mobile.iOS) + 1104
    mono_runtime_invoke_checked                                                      (in REDACTED.Mobile.iOS) + 148
    create_exception_two_strings                                                     (in REDACTED.Mobile.iOS) + 360
    mono_exception_from_name_two_strings_checked                                     (in REDACTED.Mobile.iOS) + 148
    create_domain_objects                                                            (in REDACTED.Mobile.iOS) + 348
    mono_runtime_init_checked                                                        (in REDACTED.Mobile.iOS) + 312
    mini_init                                                                        (in REDACTED.Mobile.iOS) + 8200
    xamarin_main                                                                     (in REDACTED.Mobile.iOS) (monotouch-main.m:425)
    main                                                                             (in REDACTED.Mobile.iOS) (main.m:236)
    
  • AkashDeepAkashDeep USMember
    edited November 2020

    Our Xamarin Forms iOS app is also experiencing the same issue where user gets a white screen on launch of the app and then it crashes. This has started happening after iOS 14.2 upgrade.

    App works fine on iOS 14.1 or other lower versions.

    Issue is on iPads with iOS 14.2 and app deployed via MDM ( Confirmed with InTUne and Apple Configurator) where iPads were enrolled 'Without User Affinity'. If we deploy the app via any MDM but with a user account linked to the device, then app works fine.

    Also, App works fine when deployed direct from App store or even when deployed via TestFlight

    We are using Xamarin.Forms 4.6

    Crash log points to EXC_BAD_ACCESS with one of the thread with Permission fault

    Exception Type: EXC_BAD_ACCESS (SIGKILL)
    Exception Subtype: UNKNOWN_0x32 at 0x000000010315c868
    VM Region Info: 0x10315c868 is in 0x10315c000-0x103160000; bytes after start: 2152 bytes before end: 14231
    REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
    VM_ALLOCATE 103158000-10315c000 [ 16K] rw-/rwx SM=PRV
    ---> mapped file 10315c000-103160000 [ 16K] r-x/r-x SM=COW ...t_id=7e0ac945
    VM_ALLOCATE 103160000-103164000 [ 16K] rw-/rwx SM=PRV

    Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000103700048 x1: 0x0000000103700018 x2: 0x0000000000000000 x3: 0x0000000000000000
    x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000
    x8: 0x0000000000000000 x9: 0x00000001028ee8d4 x10: 0x00000000000000e2 x11: 0x0000000030144000
    x12: 0x00000000fffffffd x13: 0x0000010000000000 x14: 0x000000016eebaaf8 x15: 0x000000016eebab40
    x16: 0x000000010315c868 x17: 0x000000010104dee0 x18: 0x0000000000000000 x19: 0x000000016eebab50
    x20: 0x000000016eebaea0 x21: 0x0000000000000000 x22: 0x0000000000000001 x23: 0x000000016eebaa90
    x24: 0x000000016eebab40 x25: 0x000000010581b550 x26: 0x0000000280ab8280 x27: 0x0000000102ba21f8
    x28: 0x000000010581b560 fp: 0x000000016eeba9f0 lr: 0x000000010104defc
    sp: 0x000000016eeba9f0 pc: 0x000000010315c868 cpsr: 0x60000000
    esr: 0x8200000f (Instruction Abort) Permission fault

  • I am experiencing the same issue. I posted this temporary workaround in the GitHub issues tracking this problem (xamarin-macios Issue #10086 and Xamarin.Forms Issue #12811):

    1. Deploy app via MDM.
    2. Enable "Offload App" iOS feature (Settings, General, iDevice Storage, Select app, tap "Offload App")
    3. Next time the app is launched it is downloaded again from the App Store and the app crash no longer occurs.
  • NMackayNMackay GBInsider, University admin

    Thanks for providing the links to track Iain, hope your keeping well and still creating interesting beers :)

Sign In or Register to comment.