NativeScript: Upgraded our OS to 14.2 and the enterprise app starts crashing, couldn't open it, install via MDM

Just a note there are a couple of comments in the Xamarin iOS 14.2 thread which state that is issue is fixed in 14.4 beta 2.

https://github.com/xamarin/xamarin-macios/issues/10086#issuecomment-759719642 https://github.com/xamarin/xamarin-macios/issues/10086#issuecomment-760214497

I updated one of our dev iPads to 14.4 beta 2 and deployed via MDM and the app worked! Now we just have to wait for iOS 14.4 to be released, hopefully soon!

@JamesRoome & @xuzhanqian - To set your expectation correctly, as much as we love to fix every issue reported – unless it is something really simple that the logs point to – this is very much likely not a issue that we will fix anytime soon as it will just consume too much time for the very tiny number of actual developers impacted. This issue is technically a “self-inflicted” corner case that doesn’t affect the community at large.

Since this is a 100% open source project with currently a very very small amount of funding, our limited resources are so much better served dealing with the issues that affect the majority of the community rather than any corner cases that have such a small impact to the entire eco-system. We will gratefully accept any PR’s to fix this…

Ways forward:

• Your companies dedicate employees to research and create a PR to fix this. 👍
• One (or both) of your companies fund the time for us at nStudio to research and fix it.
• One (or both) of your companies gets a enterprise support contract (which they are used to fund NS) and use one of your tickets on this issue.
• Another enterprise company using MDM steps up and does one of the above…
• Someone else from the community decides to fix it with a PR.

As such I’m marking this issue as a backlog issue… As we agree it is a real issue, and we would love to fix it, but it is not one we have the resources to fix at this point at time…

We are also seeing this crash issue. App works just fine on iOS 14.1 and below (deployed using MDM). It crashes with iOS 14.2 when deployed using an MDM tool (works fine with normal deployment).

Our MDM provider sent us this link for troubleshooting: https://developer.apple.com/forums/thread/666399

The Xamarin team have a fix, but it is very Xamarin specific (https://github.com/xamarin/xamarin-macios/issues/10086#issuecomment-738237870). Looking for a NativeScript fix.

I’ll be getting my development tablet setup with an MDM today, so will hopefully be able to followup with the vendor.js info.

Just a note there are a couple of comments in the Xamarin iOS 14.2 thread which state that is issue is fixed in 14.4 beta 2.

xamarin/xamarin-macios#10086 (comment) xamarin/xamarin-macios#10086 (comment)

I updated one of our dev iPads to 14.4 beta 2 and deployed via MDM and the app worked! Now we just have to wait for iOS 14.4 to be released, hopefully soon!

Can confirm this for iPhone SE running 14.4 Beta 2 deploying via MDM worked fine.

@tmedora - You can send a email to us at support@nstudio.io it will go into our support queue and one of us at nStudio will respond. 😉

Not N related. Xamarin is facing the same issue https://github.com/xamarin/xamarin-macios/issues/10086. Apparently Apple is about to release a fix https://github.com/xamarin/xamarin-macios/issues/10086#issuecomment-743395597

After the N7 demo was approved by Apple, it was installed on 14.2 devices through MDM, but it still crashed. This is the latest Crashlog, it seems that the problem still exists notify_get_state check indicated test daemon not ready.

09:37:35.248048+0800	 	networkd_settings_read_from_file initialized networkd settings by reading plist directly
09:37:35.248117+0800	 	networkd_settings_read_from_file initialized networkd settings by reading plist directly
09:37:35.253038+0800	 	nw_path_evaluator_start [679A41C0-F7D6-467D-9AB2-6B5A787F9560 <NULL> generic, indefinite]
path: satisfied (Path is satisfied), interface: en0, ipv4, dns
09:37:35.510298+0800	 	Cache loaded with 4644 pre-cached in CacheData and 53 items in CacheExtra.
09:37:35.576811+0800	 	Initializing connection
09:37:35.576863+0800	 	Removing all cached process handles
09:37:35.576941+0800	 	Sending handshake request attempt #1 to server
09:37:35.577043+0800	 	Creating connection to com.apple.runningboard
09:37:35.578388+0800	 	Handshake succeeded
09:37:35.578423+0800	 	Identity resolved as application<com.xxxxx.xxx>
09:37:35.950232+0800	 	[FBSDisplaySource 1-1] silently connecting <FBSDisplayConfiguration: 0x283c08fc0; Main; mode: "414x896@2x 60Hz p3 SDR">
09:37:35.950294+0800	 	[FBSDisplaySource 1-1] initialized <FBSDisplayConfiguration: 0x283c08fc0; Main; mode: "414x896@2x 60Hz p3 SDR">
09:37:35.953552+0800	 	FBSWorkspace connecting to endpoint : <private>
09:37:35.953583+0800	 	FBSWorkspace registering source: <private>
09:37:35.953788+0800	 	FBSWorkspace connected to endpoint : <private>
09:37:35.953834+0800	 	Added observer for process assertions expiration warning: <_RBSExpirationWarningClient: 0x28052db40>
09:37:35.955166+0800	 	Registering for test daemon availability notify post.
09:37:35.955877+0800	 	notify_get_state check indicated test daemon not ready.

Is it possible to solve this problem with NativeScript Framwork? Or is it apple’s problem?

at run(file:///app/vendor.js:92762:26)

This is code at vendor.js:92762. This method leads to Crash, but it does nothing.

if (!iosApp.nativeApp) { UIApplicationMain(0, null, null, iosApp && iosApp.delegate ? NSStringFromClass(iosApp.delegate) : NSStringFromClass(Responder)); }