Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

iOS 14.2 app crashes if deployed via mdm but not from appstore #10086

Closed
kodejack opened this issue Nov 11, 2020 · 219 comments
Closed

iOS 14.2 app crashes if deployed via mdm but not from appstore #10086

kodejack opened this issue Nov 11, 2020 · 219 comments
Labels
bug If an issue is a bug or a pull request a bug fix iOS Issues affecting Xamarin.iOS
Milestone
Future

Comments

@kodejack
Copy link

kodejack commented Nov 11, 2020 •
edited by dalexsoto
Loading

🚨⚠️🚨⚠️🚨⚠️🚨⚠️

See current proposed solution

🚨⚠️🚨⚠️🚨⚠️🚨⚠️

Steps to Reproduce

  1. The App has been built using Azure Devop pipelines it is then deployed to AppStore connect Via Fastlane
  2. The App is then deployed to devices via Mobile Iron
  3. Most apps are working but the combination of MobileIron, iOS 14.2 and it seems iPhone 11 are causing the issue described in the post.
  4. On iOS 14.1 - iPhone 11 everything works as expected see forum post.

https://forums.xamarin.com/discussion/186138/ios-14-2-app-crashes-if-deployed-via-mdm-but-not-from-appstore

Expected Behavior

The App shout start normally

Actual Behavior

The app crashes on start as it takes to long to start.

Environment

iOS 14.2 built with Mac OS 10.15.
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md

Symbolicated StackTrace

    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)

Crash Report

Incident Identifier: 7A338BC3-9B9D-45BA-8367-6D2C7DB38D54
CrashReporter Key: 0a7f5514b1eabef9a9ced769aec120d56c1212d7
Hardware Model: iPhone12,1
Process: REDACTED.Mobile.iOS [441]
Path: /private/var/containers/Bundle/Application/ACDDB724-517E-4FC1-B07E-DEAEE9FE213A/REDACTED.Mobile.iOS.app/REDACTED.Mobile.iOS
Identifier: REDACTED
Version: 2011041216 (1.0.1)
AppStoreTools: 12A7604b
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: REDACTED [411]

Date/Time: 2020-11-09 14:53:13.4760 +0000
Launch Time: 2020-11-09 14:52:53.4304 +0000
OS Version: iPhone OS 14.2 (18B92)
Release Type: User
Baseband Version: 2.02.04
Report Version: 104

Exception Type: EXC_BAD_ACCESS (SIGKILL)
Exception Subtype: UNKNOWN_0x32 at 0x0000000105c908a8
VM Region Info: 0x105c908a8 is in 0x105c90000-0x105c94000; bytes after start: 2216 bytes before end: 14167
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
VM_ALLOCATE 105c8c000-105c90000 [ 16K] rw-/rwx SM=PRV
---> mapped file 105c90000-105c94000 [ 16K] r-x/r-x SM=COW ...t_id=5d9c747d
VM_ALLOCATE 105c94000-105c98000 [ 16K] rw-/rwx SM=PRV

Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:process-launch watchdog transgression: application: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>
Triggered by Thread: 0
@mlancione
Copy link

I am experiencing the same issue with Xamarin.iOS (14.4.1.3) apps as well. The app crash only occurs if the app is deployed via MDM (AirWatch) from the App Store and does not occur if the app is built as an IPA and deployed via MDM.

The following workaround resolves the app crash:

  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.

@spouliot
Copy link
Contributor

The app are build identically for AppStore / AdHoc / MDM.

The code:0x8BADF00D means the watchdog killed the app since it took too much time to startup. It's possible that some 3rd party code is trying to do something different (e.g. reach a server) and that cause an unacceptable delay.

@kodejack can you open the console app and give us the logs from the device where this happens (between the app start and it's crash 20 seconds later). It's possible that either us, some 3rd party or the OS has logged warnings/errors that could shed some light on what went wrong. Thanks!

@spouliot spouliot added the need-info Waiting for more information before the bug can be investigated label Nov 12, 2020
@rachelkang rachelkang mentioned this issue Nov 12, 2020
Closed
@mlancione

This comment has been minimized.

Sign in to view
@spouliot
Copy link
Contributor

@kodejack thanks for the logs! First quick look there's nothing in or out process that clearly explain why the process has not launched inside the 20 seconds limit.

@dalexsoto did mention to me that loaded libraries are arm64e even if the process itself is arm64. Not sure if that's an issue or just an updated way to show the information.

0x102b4c000 - 0x10557ffff REDACTED.Mobile.iOS arm64  <ce7bc43f91e83838925615408c5813fc> /var/containers/Bundle/Application/ACDDB724-517E-4FC1-B07E-DEAEE9FE213A/REDACTED.Mobile.iOS.app/REDACTED.Mobile.iOS
0x105ebc000 - 0x105f2bfff dyld arm64e  <a5f65ef3bd32370b9821b3e9cda294d2> /usr/lib/dyld
...

@spouliot
Copy link
Contributor

sorry I mean @mlancione above.

Looking again at the forum post ot seems to affect only newer phones, i.e. those with arm64e CPU. I would guess there's a bug, on Apple side, where the app is optimized for an unsupported architecture. If you have not already I would file a feedback issue with Apple so they can confirm this.

@kodejack
Copy link
Author

We have posted an issue to Apple as well, I'll pass on the comment about arm64e. I'll get logs from the device directly.

@stewart-rae
Copy link

@spouliot and @kodejack - Same issue with us, and same information recorded in the crash dump about arm64 / arm64e architecture:

Binary Images:
0x104338000 - 0x105faffff REDACTED.Mobile.iOS **arm64**  <60fc0967b84d315cba71ce474a67af15> /var/containers/Bundle/Application/258A589B-591B-4E47-B78F-D99BFD40508C/REDACTED.Mobile.iOS.app/REDACTED.Mobile.iOS
0x106580000 - 0x1065effff dyld **arm64e**  <a5f65ef3bd32370b9821b3e9cda294d2> /usr/lib/dyld
0x1855eb000 - 0x18562dfff libdispatch.dylib **arm64e**  <3277bf1eb99436099b30e0186bbf3c25> /usr/lib/system/libdispatch.dylib
... etc

@stewart-rae
Copy link

@mlancione unfortunately, we tried the "Offload App" workflow that you suggested, and this didn't fix the issue. Our app still crashes.

@spouliot
Copy link
Contributor

@stewart-rae thanks for confirming! Multiple, consistent reports are helpful, otherwise we might end up investigating the wrong things :-)

@cheles
Copy link

cheles commented Nov 13, 2020

I know you are aware @spouliot but just to avoid duplicate issues, there is also an one opened on Xamarin.Forms

@DerPate2010
Copy link

@spouliot Not sure if it helps: I'm working at Microsoft and have 2 customer apps affected by this. In both cases the apps are built by Microsoft. So it is easy to give you access to the full apps and source code internally.

None of the apps are using a MDM SDK.
One app is reading AppConfig, the other not.
The only libaries in common are Xamarin.Forms and Xamarin.Core.
Both apps use sqlite but different libs: SQLitePCLRaw.bundle_e_sqlite3 and SQLitePCLRaw.bundle_green
I have the impression that the app crashes before any Xamarin.Forms, SQlite or AppConfig code is invoked.

@b099l3
Copy link

b099l3 commented Nov 13, 2020

Tried the "Offload App" workflow too did not seem to fix this issue.

I have attached the crash log for the App @kodejack and I are working on:
LogOfiOSAppCrash142MDM.txt

I have redacted the app name and bundle id with REDACTED.APP.NAME and REDACTED.BUNDLE.ID if you want to search the log.

Here are some more details for the app:

  • Using native Xamarin.iOS we are not using Xamarin.Forms - not sure if this is important
  • The App is deployed from various environments and then uploaded to MDM (UAT, SIT, Pre-Prod) - these all work
  • The difference with this app and the others is it the AppStore version and has been uploaded to TestFlight first then MDM, this is used to get automatic updates from MDM - this is where I think the issue lies

@divil5000

This comment has been minimized.

Sign in to view
@b099l3
Copy link

b099l3 commented Nov 13, 2020

I was able to test the deployed build from TestFlight not going through MDM and it doesnt crash on startup, it would appear that something in MDM is causing it to hit the time limit on start up?

I thought it might be a combination of MDM, loading a config and other startup tasks which is causing the issue but an iPhone 6S Plus, which I would assume would take longer to start up the app, does not crash...

Just to note this issue doesnt happen on:
iPhone 6s Plus with iOS 14.2
iPhone 7 Plus with iOS 14.2

This is all very speculative but it would appear that the issue is pointing towards MDM and the arm64e CPU devices?

@6ril

This comment has been minimized.

Sign in to view
@mlancione
Copy link

Link to issue reported on Apple's dev forums:
https://developer.apple.com/forums/thread/666399

@spouliot
Copy link
Contributor

Everyone Please file a feedback ticket with Apple with your specific information.

Also make sure to link this https://feedbackassistant.apple.com/feedback/8895585 ticket (in the text) so they can all be seen as a single issue.

Thanks!

@akashvashisht
Copy link

akashvashisht commented Nov 15, 2020 •
edited
Loading

@spouliot : We had raised a ticket with Apple's Developer Technical Support and shared all this info.

This is the reply from Apple's DTS engineer :

Us:

One thing we have noticed is, the main process is 'arm64', but the
rest of the libraries are all 'arm64e'. Is this significant at all?

Apple's reply
arm64e binaries are valid as long as they are Apple loaded binaries, which yours are.
arm64e binaries are only an issue if you are creating your app with this architecture, which you are not.

We shared these logs :

#8 (null) in plcrash::MS::async::dwarf_cfa_state_iterator<unsigned
long long, long long>::next+ 27004828 (unsigned int*,
plcrash::MS::async::plcrash_dwarf_cfa_reg_rule_t*, unsigned long
long*) ()
#9 (null) in plcrash::MS::async::dwarf_cfa_state_iterator<unsigned
long long, long long>::next+ 26881808 (unsigned int*,
plcrash::MS::async::plcrash_dwarf_cfa_reg_rule_t*, unsigned long
long*) ()
#10 (null) in xamarin_release_block_on_main_thread ()
#11 (null) in plcrash::MS::async::dwarf_cfa_state_iterator<unsigned
long long, long long>::next+ 412676 (unsigned int*,
plcrash::MS::async::plcrash_dwarf_cfa_reg_rule_t*, unsigned long
long*) ()
#12 (null) in 0x18562e000 ()

Apple's reply : First, it does look like you are using xamarin here, "xamarin_release_block_on_main_thread," if I am correct I should let you know that DTS does not support Xamarin and this is something you would have to contact the vendor about.

@halderp
Copy link

halderp commented Nov 16, 2020

Our App and many users are impacted by this issue. Is there any solution to this ?

@MarteFP
Copy link

MarteFP commented Nov 16, 2020 •
edited
Loading

Hi! We are wondering the same as above. Thousands of users can be affected. Is the rootcause found? We follow this thread for updates :)

@leonluc-dev
Copy link

leonluc-dev commented Nov 16, 2020 •
edited
Loading

Similar issues on iOS 14.2 here as well. We have customers with MDM deployments and most have a similar issue: The app hangs during startup and closes after 15 seconds (which implies the OS kills the app due to the 15 second startup limit). The logs indicate a hang on wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr (same as earlier logs shared in this issue).

So far the MDM environments where this issue occurs are:
-MobileIron
-Microsoft Intune
-VMWare Workspace ONE

The issue can seemingly occur on multiple kinds of iOS devices (we have received reports from customers running into issues on the iPhone 7, 2nd gen iPhone SE, iPhone XR and iPhone 11).
There have been cases where within a single MDM environment some iOS 14.2 users could open the app while some couldn't, we haven't been able to establish a pattern there. (It turns out the pattern was ARM64e devices)

Running our app in these MDM environments on iOS 14.1 (and earlier) still works as expected.

@spouliot
Copy link
Contributor

spouliot commented Nov 16, 2020 •
edited
Loading

@leonluc-dev so far you are the only one reporting this issue happening on earlier arm64 CPU. Other reports are on newer phones only, with arm64e CPU. Please make sure to mention that on the feedback you supply to Apple and don't forget to link to our own ticket https://feedbackassistant.apple.com/feedback/8895585

@mlancione
Copy link

mlancione commented Nov 16, 2020 •
edited
Loading

From this Apple forum thread it appears that NativeScript apps may also be experiencing this issue:
https://developer.apple.com/forums/thread/666045?answerId=646229022&page=1#646340022

This NativeScript thread describes a similar iOS 14 issue (but not specifically iOS 14.2):
NativeScript/NativeScript#8665

In that thread it is pointed out that the Apple iOS 14 Release Notes has this "Third Party App" Known Issues warning (https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-14-release-notes):

Apps using the NativeScript framework might quit unexpectedly on launch. NativeScript performs an unsafe operation to determine if an arbitrary pointer is an Objective-C object pointer. You can temporarily resolve this issue by using object_getClass(_:) instead of reading the isa directly; however, update this code to avoid checking whether arbitrary pointers are Objective-C object pointers. (62913064)

Is this at all relevant to our issue?

@leonluc-dev
Copy link

@spouliot Apologies. It seems the iPhone 7 report was a report mixup. So far we've been able to confirm the issue at customers using the 2nd gen iPhone SE, iPhone XR or iPhone 11 (all of them ARM64e devices)

@spouliot
Copy link
Contributor

@mlancione that's recent but not new in 14.2. AFAIK this should not be an issue but we'll be double-checking this. Thanks!

@halderp
Copy link

halderp commented Nov 16, 2020 •
edited
Loading

We are seeing this issue with the following MDMs as well:

  • Airwatch

@bjenkins12
Copy link

We are seeing this issue on an AirWatch MDM deployed xamarin app to an iPhone XR running iOS 14.2.

Our app works fine when not deployed via AirWatch MDM (downloaded straight from app store).

Our app works fine when deployed via AirWatch MDM to iphone XR running iOS 14.1 and below.

@marcodelfrari
Copy link

Same problem here and this is very critical for us (we are using Intune as MDM)

@jpeters5392
Copy link

jpeters5392 commented Jan 8, 2021 via email

@pranavtiwa
Copy link

pranavtiwa commented Jan 8, 2021 •
edited
Loading

@jpeters5392 @leonluc-dev
Exception Type: EXC_BAD_ACCESS (SIGKILL)
Exception Subtype: UNKNOWN_0x32 at 0x00000001082f87e8
VM Region Info: 0x1082f87e8 is in 0x1082f8000-0x1082fc000; bytes after start: 2024 bytes before end: 14359
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
VM_ALLOCATE 1082f4000-1082f8000 [ 16K] rw-/rwx SM=PRV
---> mapped file 1082f8000-1082fc000 [ 16K] r-x/r-x SM=COW ...t_id=3cc629b7
VM_ALLOCATE 1082fc000-108300000 [ 16K] rw-/rwx SM=PRV

Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:process-launch watchdog transgression: application<***>:1346 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): 23.430 (user 23.430, system 0.000), 20% CPU", | "Elapsed application CPU time (seconds): 19.877, 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 ??? 0x00000001082f87e8 0 + 4432300008

This is the crash log but i couldn't find anything related to exhausted trampolines

@jpeters5392
Copy link

jpeters5392 commented Jan 8, 2021 via email

@AlfDoej
Copy link

AlfDoej commented Jan 12, 2021 •
edited
Loading

STATUS ON THIS ISSUE? ANYONE? :-)
As a Project PO i'm very interested in any updates on this issue.
We have clients that are using all types of MDM/MAM tools - and all report the same with apps distributed to iOS devices with unit-OS higher than iOS 14.1..

  • Does anyone know if this issues relates to Xamarin or iOS?
  • Any news regarding a permanent fix

@sankar12345
Copy link

sankar12345 commented Jan 12, 2021 via email

@spouliot
Copy link
Contributor

@sankar12345 there are several type of trampolines. Please tell us every option being provided to the Additional mtouch arguments

@sankar12345
Copy link

sankar12345 commented Jan 12, 2021 via email

@AlfDoej
Copy link

AlfDoej commented Jan 13, 2021

DOES iOS 14.3 solve the MDM issues?

An iOS update is ready now - the 14.3.. Did anyone have the chance to test if this one solves any issues?

@leonluc-dev
Copy link

@AlfDoej For us 14.3 did not solve the MDM issues. The trampoline workaround described earlier still works though.

@gdarm
Copy link

gdarm commented Jan 13, 2021

Bug seems to have been fixed in iOS 14.4 Beta 2.

Can anyone confirm please?

@jpsweet
Copy link

jpsweet commented Jan 13, 2021

Yes, I can confirm.

@vargaz
Copy link
Contributor

vargaz commented Jan 13, 2021

@sankar12345 nrgctx-fetch-trampolines=4096 should be enough, why did you have to double it, was there a failure without it ?

@spouliot
Copy link
Contributor

We have not heard back from Apple but I can confirm too that a "known to be broken" app works fine with 14.4 beta 2.
The same app downloaded to a 14.3 device still has the issue, so it seems related to the iOS update (or a version check in the hardening process).

@sankar12345
Copy link

sankar12345 commented Jan 13, 2021 via email

@spouliot
Copy link
Contributor

I got in touch with Apple DTS and they confirmed me that the new iOS 14.4 beta 2 beta does have the fix we were waiting for. This means the workaround won't be needed once customers upgrade to the final, public release of iOS 14.4.

Sadly this also means that the workaround is required as long as you wish to support MSM deployment on iOS 14.2 and 14.3.

We'll continue to test each new beta until a public/stable iOS release ships with the fix.

@pranavtiw
Copy link

@spouliot any timeline for release of 14.4 ..??

@spouliot
Copy link
Contributor

@pranavtiw no, that's iOS (not Xamarin) so you'll need to ask Apple for timelines :-)

You can try to guesstimate a date using https://xcodereleases.com - but, so far, there's not Xcode associated with iOS 14.4.

There's a rumour of an event in March. New version of iOS are often required when releasing new hardware model... but neither the event nor the required update are certainties.

@udayvalluri
Copy link

udayvalluri commented Jan 22, 2021 •
edited
Loading

@spouliot

If Apple fixes this in 14.4 (Public Release), do the users need to update their devices to 14.4 OS or we need to build the application with the latest XCode(comes with iOS 14.4) and then redeploy it to MDM servers?

@spouliot
Copy link
Contributor

I just tested iOS 14.4 RC (release candidate) and it works fine.

@udayvalluri existing "broken" applications works fine with iOS 14.4. This means the only requirement will be for your users to update to iOS 14.4.

If you used the workaround then you might want to remove it - now or later.

Be aware that removing it will break MDM-users running iOS 14.2 and 14.3.

@jdinnen
Copy link

jdinnen commented Jan 26, 2021

I got in touch with Apple DTS and they confirmed me that the new iOS 14.4 beta 2 beta does have the fix we were waiting for. This means the workaround won't be needed once customers upgrade to the final, public release of iOS 14.4.

Sadly this also means that the workaround is required as long as you wish to support MSM deployment on iOS 14.2 and 14.3.

We'll continue to test each new beta until a public/stable iOS release ships with the fix.

Working on iOS 14.4 public release that I just downloaded from official OTA update...

@davembond
Copy link

Thanks for all the info and updates. It's greatly appreciated.

I can verify as well that applying iOS 14.4 RC resolves the issue for our customers.

@cwolff-wells
Copy link

Just here confirming this also fixed NativeScript apps as well. Let's all have a party

@spouliot
Copy link
Contributor

The final iOS 14.4 version is the same as the release candidate. To avoid any doubt I updated a different phone to make my last checks - and it worked like expected.

A huge thank you to everyone who reported the issues, both to us and Apple. Additional ❤️ for everyone who provided additional informations, crash logs, time and who helped others.

@sankar12345
Copy link

sankar12345 commented Feb 2, 2021 via email

@Reshma9006
Copy link

Hi,
Currently I am noticing the same issue again in iPad OS 14.5.1, on arm64e devices like iPad Air 3 (Distributed through Intune)even with the the workaround
Works fine in arm64 devices on 14.5.1, Does anyone have any idea on this?
Earlier It was working fine in 14.3,14.4 with workaround.

--Error Logs--
error 15:16:08.449435+0200 containermanagerd -MCMClientConnection createOrLookupContainerWithContainerIdentity:createIfNecessary:transient:useLocking:withError:: com.siemensgamesa.DTS not entitled to retrieve container class 7 with identifier group.com.microsoft.shared
error 15:16:08.450048+0200 containermanagerd [0] command=38, client=<<~~~>, u=<501/501//0/1000>, uid=501, pid=471, sandboxed=1, platform=2>, error=55 (NOT_ENTITLED_FOR_OPERATION)
error 15:16:08.451426+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
error 15:16:08.452429+0200 containermanagerd -MCMClientConnection createOrLookupContainerWithContainerIdentity:createIfNecessary:transient:useLocking:withError:: com.siemensgamesa.DTS not entitled to retrieve container class 7 with identifier group.com.microsoft.shared-df
error 15:16:08.452632+0200 containermanagerd [0] command=38, client=<<~~~>, u=<501/501//0/1000>, uid=501, pid=471, sandboxed=1, platform=2>, error=55 (NOT_ENTITLED_FOR_OPERATION)
error 15:16:08.452805+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
error 15:16:08.452982+0200 DTS A NULL string is not a valid group container identifier.
error 15:16:08.453084+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client sent invalid parameters
error 15:16:08.457830+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /private/etc/.mdns_debug
error 15:16:08.481163+0200 kernel Sandbox: DTS(471) deny(1) file-read-data /private/var/mobile/Containers/Data/PluginKitPlugin
error 15:16:08.481817+0200 kernel Sandbox: DTS(471) deny(1) file-read-data /private/var/mobile/Containers/Shared/AppGroup
error 15:16:08.483786+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
error 15:16:08.485301+0200 containermanagerd -MCMClientConnection createOrLookupContainerWithContainerIdentity:createIfNecessary:transient:useLocking:withError:: com.siemensgamesa.DTS not entitled to retrieve container class 7 with identifier group.com.microsoft.shared
error 15:16:08.486037+0200 containermanagerd [0] command=38, client=<<~~~>, u=<501/501//0/1000>, uid=501, pid=471, sandboxed=1, platform=2>, error=55 (NOT_ENTITLED_FOR_OPERATION)
error 15:16:08.488210+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
error 15:16:08.488291+0200 DTS A NULL string is not a valid group container identifier.
error 15:16:08.488339+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client sent invalid parameters
error 15:16:08.489675+0200 containermanagerd -MCMClientConnection createOrLookupContainerWithContainerIdentity:createIfNecessary:transient:useLocking:withError:: com.siemensgamesa.DTS not entitled to retrieve container class 7 with identifier group.com.microsoft.shared-df
error 15:16:08.489793+0200 containermanagerd [0] command=38, client=<<~~~>, u=<501/501//0/1000>, uid=501, pid=471, sandboxed=1, platform=2>, error=55 (NOT_ENTITLED_FOR_OPERATION)
error 15:16:08.505647+0200 kernel Sandbox: DTS(471) deny(1) file-read-data /private/var/mobile/Containers/Data/PluginKitPlugin
error 15:16:08.505945+0200 kernel Sandbox: DTS(471) deny(1) file-read-data /private/var/mobile/Containers/Shared/AppGroup
error 15:16:08.507410+0200 containermanagerd -MCMClientConnection createOrLookupContainerWithContainerIdentity:createIfNecessary:transient:useLocking:withError:: com.siemensgamesa.DTS not entitled to retrieve container class 7 with identifier group.com.microsoft.shared
error 15:16:08.507600+0200 containermanagerd [0] command=38, client=<<~~~>, u=<501/501//0/1000>, uid=501, pid=471, sandboxed=1, platform=2>, error=55 (NOT_ENTITLED_FOR_OPERATION)
error 15:16:08.508306+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
error 15:16:08.509407+0200 containermanagerd -MCMClientConnection createOrLookupContainerWithContainerIdentity:createIfNecessary:transient:useLocking:withError:: com.siemensgamesa.DTS not entitled to retrieve container class 7 with identifier group.com.microsoft.shared-df
error 15:16:08.509768+0200 containermanagerd [0] command=38, client=<<~~~>, u=<501/501//0/1000>, uid=501, pid=471, sandboxed=1, platform=2>, error=55 (NOT_ENTITLED_FOR_OPERATION)
error 15:16:08.509951+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client is not entitled
error 15:16:08.510189+0200 DTS A NULL string is not a valid group container identifier.
error 15:16:08.510261+0200 DTS container_create_or_lookup_app_group_path_by_app_group_identifier: client sent invalid parameters
error 15:16:10.275283+0200 wifid __WiFiManagerDispatchLQMEvent: Dispatching LQM event to symptomsd
error 15:16:10.493012+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /usr/bin/gdb
error 15:16:10.493125+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /bin/gdb
error 15:16:10.493238+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /sbin/gdb
error 15:16:10.493300+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /usr/bin/lldb
error 15:16:10.493364+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /bin/lldb
error 15:16:10.493424+0200 kernel Sandbox: DTS(471) deny(2) file-test-existence /sbin/lldb
error 15:16:14.137635+0200 duetexpertd Can't use store bookmark for stream: POICategory, since the input bookmark object is invalid
error 15:16:14.137765+0200 duetexpertd Failed to create new framestore with nil filename
error 15:16:14.137891+0200 duetexpertd Unable to open framestore with error: Error Domain=com.apple.biome.BiomeStorage Code=-1 "Failed to create new framestore with nil filename" UserInfo={NSLocalizedDescription=Failed to create new framestore with nil filename}
error 15:16:14.164552+0200 duetexpertd Can't use store bookmark for stream: AppIntent, since the input bookmark object is invalid
error 15:16:14.171298+0200 duetexpertd Failed to create new framestore with nil filename
error 15:16:14.171456+0200 duetexpertd Unable to open framestore with error: Error Domain=com.apple.biome.BiomeStorage Code=-1 "Failed to create new framestore with nil filename" UserInfo={NSLocalizedDescription=Failed to create new framestore with nil filename}
error 15:16:14.180869+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.182279+0200 duetexpertd - Current subscription is in a recursion. StreamId: clientModel
error 15:16:14.211492+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:14.211760+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:14.212091+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:14.241642+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.246637+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.246773+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.247178+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.248239+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.249166+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.249738+0200 duetexpertd - Current subscription is in a recursion. StreamId: AppLaunch
error 15:16:14.250230+0200 duetexpertd - Current subscription is in a recursion. StreamId: AppLaunch
error 15:16:14.251259+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.252438+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.279532+0200 duetexpertd - Current subscription is in a recursion. StreamId: AppLaunch
error 15:16:14.284096+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.367355+0200 duetexpertd Can't use store bookmark for stream: AppIntent, since the input bookmark object is invalid
error 15:16:14.386269+0200 duetexpertd Failed to create new framestore with nil filename
error 15:16:14.386413+0200 duetexpertd Unable to open framestore with error: Error Domain=com.apple.biome.BiomeStorage Code=-1 "Failed to create new framestore with nil filename" UserInfo={NSLocalizedDescription=Failed to create new framestore with nil filename}
error 15:16:14.443423+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:14.449899+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:14.450323+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:14.477653+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.478990+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.479232+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.480238+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.481472+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.482428+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:14.482904+0200 duetexpertd - Current subscription is in a recursion. StreamId: AppLaunch
error 15:16:14.483637+0200 duetexpertd - Current subscription is in a recursion. StreamId: AppLaunch
error 15:16:14.484610+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.486342+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.504802+0200 duetexpertd - Current subscription is in a recursion. StreamId: AppLaunch
error 15:16:14.509912+0200 duetexpertd - Current subscription is in a recursion. StreamId: predictionContext
error 15:16:14.606168+0200 duetexpertd Can't use store bookmark for stream: POICategory, since the input bookmark object is invalid
error 15:16:14.606730+0200 duetexpertd Failed to create new framestore with nil filename
error 15:16:14.607172+0200 duetexpertd Unable to open framestore with error: Error Domain=com.apple.biome.BiomeStorage Code=-1 "Failed to create new framestore with nil filename" UserInfo={NSLocalizedDescription=Failed to create new framestore with nil filename}
error 15:16:14.989490+0200 duetexpertd - unable to load NSUserDefaults suite
error 15:16:15.024161+0200 duetexpertd - unable to load NSUserDefaults suite
error 15:16:15.096467+0200 duetexpertd - unable to load NSUserDefaults suite
error 15:16:15.298199+0200 wifid __WiFiManagerDispatchLQMEvent: Dispatching LQM event to symptomsd
error 15:16:16.185153+0200 duetexpertd - unable to load NSUserDefaults suite
error 15:16:16.216094+0200 dasd Activity not tracked as being started, ignoring it
error 15:16:18.377177+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:18.377917+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:18.378436+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:18.378779+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.379390+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.379724+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.380238+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.380603+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.381056+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.381448+0200 duetexpertd - Current subscription is in a recursion. StreamId: homeScreen
error 15:16:18.410923+0200 duetexpertd - Current subscription is in a recursion. StreamId: blending
error 15:16:20.324733+0200 wifid __WiFiManagerDispatchLQMEvent: Dispatching LQM event to symptomsd
error 15:16:25.353136+0200 wifid __WiFiManagerDispatchLQMEvent: Dispatching LQM event to symptomsd
error 15:16:28.386286+0200 SpringBoard [application<com.siemensgamesa.DTS>:471] Watchdog <FBProcessWatchdog: 0x281e4b520; name: scene-create; time: 17.72s> provision violated: <FBSProcessResourceProvision: 0x281274e00; allowance: <; FBSProcessResourceAllowance; type: realTime; timeValue: 17.72s>>
error 15:16:28.386832+0200 SpringBoard [application<com.siemensgamesa.DTS>:471] Watchdog termination request provided: <FBSProcessTerminationRequest: 0x28286e140; label: "watchdog provision violated"; exceptionCode: "Watchdog Violation (0x8BADF00D)"; reportType: CrashLog; explanation: "scene-create watchdog transgression: application<com.siemensgamesa.DTS>:471 exhausted real (wall clock) time allowance of 17.72 seconds">
error 15:16:28.387408+0200 SpringBoard [application<com.siemensgamesa.DTS>:471] Provision violated for watchdog scene-create: <FBSProcessResourceProvision: 0x281274e00; allowance: <; FBSProcessResourceAllowance; type: realTime; timeValue: 17.72s>; violated: YES>
error 15:16:28.404810+0200 runningboardd RBSStateCapture remove item called for untracked item <RBProcessMonitorObserver| qos:0 qos:(null) configs:{
}>
error 15:16:28.426439+0200 SpringBoard Unable to get short BSD proc info for 471: No such process
error 15:16:28.437488+0200 SpringBoard Unable to get short BSD proc info for 471: No such process
error 15:16:28.457950+0200 SpringBoard Error acquiring assertion: <Error Domain=RBSAssertionErrorDomain Code=2 "Specified target process does not exist" UserInfo={NSLocalizedFailureReason=Specified target process does not exist}>
error 15:16:28.471308+0200 SpringBoard HW kbd: Failed to set keyboard focus pid:0 ((null)) scene:(null)
error 15:16:28.504766+0200 SpringBoard HW kbd: Failed to set keyboard focus pid:0 ((null)) scene:(null)
error 15:16:28.505220+0200 SpringBoard tried to remove an assertion that was never added: <SBFloatingDockBehaviorAssertion: 0x28277c800> {
pinned = NO;
animated = YES;
gesture possible = YES;
visible progress = 0.000000;
level = in app;
reason = in app;
timestamp = 2021-05-19 13:16:08 +0000;
}
error 15:16:28.519468+0200 SpringBoard Error creating the CFMessagePort needed to communicate with PPT.
error 15:16:28.554522+0200 runningboardd RBSStateCapture remove item called for untracked item 34-62-706 (target:application<com.siemensgamesa.DTS>:471)
error 15:16:30.382106+0200 wifid __WiFiManagerDispatchLQMEvent: Dispatching LQM event to symptomsd

@mlancione
Copy link

I'm not seeing an issue with iOS 14.5.1. I've tested an AppStore app that contains the trampolines workaround that is deployed via MDM to an arm64e iPad and it seems to be working fine. Has anyone else seen issues yet?

@Reshma9006
Copy link

I'm not seeing an issue with iOS 14.5.1. I've tested an AppStore app that contains the trampolines workaround that is deployed via MDM to an arm64e iPad and it seems to be working fine. Has anyone else seen issues yet?

Hi,
Yes we have 2 IOS Apps, this behavior is being noticed only for this particular app, the other one works fine with arm64e devices.
Also the App which crashes on Splash screen in 14.5.1 , works fine if deployed via Test flight or Deployed directly to the device.
So unable to Identify the root cause.
In Device Logs i could see the following Error
Any suggestions would help

error 15:16:14.606730+0200 duetexpertd Failed to create new framestore with nil filename
error 15:16:14.607172+0200 duetexpertd Unable to open framestore with error: Error Domain=com.apple.biome.BiomeStorage Code=-1 "Failed to create new framestore with nil filename" UserInfo={NSLocalizedDescription=Failed to create new framestore with nil filename}

Thanks in Advance,
Reshma

@1oo7
Copy link

1oo7 commented Nov 17, 2021

Did you ever find out why this was specific to MDM? I'm facing a kind of similar issue with my private app, not related to Xamarin, but also the crash we are seeing only happens on iOS 14 (not 15). After analyzing a lot of logs and stack traces I suspect it may be a trampolines-related bug, but what I don't understand is, why MDM? What is different about an MDM install? Any insights you could offer would be super-appreciated. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug If an issue is a bug or a pull request a bug fix iOS Issues affecting Xamarin.iOS
Projects
None yet
Milestone
Future
Development

No branches or pull requests