App crashed in ios 14.2

Hi,

We have experienced the same issue.
App deployed through MobileIron MDM using the Volume Purchase Program. Since updating the device to iOS 14.2 the app crashes on start up.
Issue seems to occur only on iPhone11.
The same app is deployed to iPhone 7+ and 8+ with no issues. App was working fine until the iOS update to 14.2. See GitHub forum thread for lots of other developers experiencing the same issue with various other MDM’s.
Apps works fine if downloaded via TestFlight, the issue seems happen only when importing the app via the VPP program.
On the GitHub issue #10086 they have suggested it may be related to devices with arm64e chipset
Crash log:
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)
wrapperruntimeinvokeobjectruntimeinvokedynamicintptrintptrintptrintptr (in REDACTED.Mobile.iOS) + 260
monojitruntimeinvoke (in REDACTED.Mobile.iOS) + 1104
monoruntimeinvokechecked (in REDACTED.Mobile.iOS) + 148
createexceptiontwostrings (in REDACTED.Mobile.iOS) + 360
monoexceptionfromnametwostringschecked (in REDACTED.Mobile.iOS) + 148
createdomainobjects (in REDACTED.Mobile.iOS) + 348
monoruntimeinitchecked (in REDACTED.Mobile.iOS) + 312
miniinit (in REDACTED.Mobile.iOS) + 8200
xamarinmain (in REDACTED.Mobile.iOS) (monotouch-main.m:425)
main (in REDACTED.Mobile.iOS) (main.m:236)

Out of interest, was your app developed using any framework?
Ours was developed using xamarin and it would be useful to know if the issue lies with Microsoft rather than Apple.

It looks like this is the same issue reported here:
https://developer.apple.com/forums/thread/666399

Hi, You have marked this issue as solved. If so, could you please explain, how you resolved this issue?