[ANR] triggered by slow operations in main thread while executing com.microsoft.intune.mam.client.app.MAMComponents.get()

[singh-srikant]

Summary

We are seeing a spike in Android14 specific ANR while executing com.microsoft.intune.mam.client.app.MAMComponents.get(MAMComponents.java:652). It has 5.1K events affecting 4.2K users over the last 7 days. We updated the Intune version to 10.4.1 in our latest release. Most of the occurrences are on Android 14 devices.

Has there been any changes around this method which causes it to take more time than it was taking previously ?
Have other clients reported that they are facing this issue ?

Details

• Intune Android App SDK Version: 10.4.1
• Gradle Enterprise Plugin: "3.5.1"
• AGP Version: 8
• Android Device Make and Model: Vivo (51%), Motorola(30%), Xiaomi (12%)
• Android Device OS Version: 14 (100%)

Logs

main (runnable):tid=1 systid=13230 
#00 pc 0x4be2bc libart.so (art::DumpNativeStack + 108) (BuildId: 2452917c4ff69cbb6e75e5512260946b)
#01 pc 0x4afbd4 libart.so (art::Thread::DumpStack const + 388) (BuildId: 2452917c4ff69cbb6e75e5512260946b)
#02 pc 0x4af514 libart.so (art::DumpCheckpoint::Run + 164) (BuildId: 2452917c4ff69cbb6e75e5512260946b)
#03 pc 0x3c55d0 libart.so (art::Thread::RunCheckpointFunction + 148) (BuildId: 2452917c4ff69cbb6e75e5512260946b)
#04 pc 0x5ad31c libart.so (artTestSuspendFromCode + 232) (BuildId: 2452917c4ff69cbb6e75e5512260946b)
#05 pc 0x350c1c libart.so (art_quick_test_suspend + 156) (BuildId: 2452917c4ff69cbb6e75e5512260946b)
       at dalvik.system.VMStack.getThreadStackTrace(Native method)
       at java.util.logging.LogRecord.inferCaller(LogRecord.java:560)
       at java.util.logging.LogRecord.getSourceClassName(LogRecord.java:307)
       at com.microsoft.intune.mam.log.MAMLogHandlerWrapperImpl.copyPrimitiveLogRecordComponents(MAMLogHandlerWrapperImpl.java:342)
       at com.microsoft.intune.mam.log.MAMLogHandlerWrapperImpl.messageFormatRecord(MAMLogHandlerWrapperImpl.java:303)
       at com.microsoft.intune.mam.log.MAMLogHandlerWrapperImpl.messageFormatRecord(MAMLogHandlerWrapperImpl.java:284)
       at com.microsoft.intune.mam.log.MAMLogHandlerWrapperImpl.buildNoPIIRecord(MAMLogHandlerWrapperImpl.java)
       at com.microsoft.intune.mam.log.MAMLogHandlerWrapperImpl.publish(MAMLogHandlerWrapperImpl.java:164)
       at java.util.logging.Logger.log(Logger.java:738)
       at com.microsoft.intune.mam.log.MAMLogger.log(MAMLogger.java:233)
       at com.microsoft.intune.mam.log.MAMLogger.log(MAMLogger.java:252)
       at com.microsoft.intune.mam.log.MAMLogger.info(MAMLogger.java:378)
       at com.microsoft.intune.mam.client.identity.MAMIdentityManagerBase.fetchPersistedIdentities(MAMIdentityManagerBase.java:91)
       at com.microsoft.intune.mam.client.app.LazyInit.get(LazyInit.java:50)
       at com.microsoft.intune.mam.client.identity.MAMIdentityManagerBase.getIdentities(MAMIdentityManagerBase.java:340)
       at com.microsoft.intune.mam.client.app.offline.OfflineMAMUserInfo.<init>(OfflineMAMUserInfo.java:33)
       at com.microsoft.intune.mam.client.app.offline.OfflineComponents.get(OfflineComponents.java:248)
       at com.microsoft.intune.mam.client.app.MAMComponents.get(MAMComponents.java:652)
       at com.a.r.emm.intune.ARIntuneRestrictionsManager.isManagedApp(ARIntuneRestrictionsManager.java:213)
       at com.a.r.emm.AREMMManager.isIntuneManagedApp(AREMMManager.java:110)
       at com.a.r.emm.AREMMManager.isDocumentCloudStorageEnabled(AREMMManager.java:571)
       at com.a.r.ARApp.onMAMCreate(ARApp.java:573)
       at com.a.r.Hilt_ARProdApp.onMAMCreate(Hilt_ARProdApp.java:40)
       at com.microsoft.intune.mam.client.app.MAMApplication$Impl.onCreatePrimaryProcess(MAMApplication.java:193)
       at com.microsoft.intune.mam.client.app.MAMApplication$Impl.onCreate(MAMApplication.java:128)
       at com.microsoft.intune.mam.client.app.MAMApplication.onCreate(MAMApplication.java)
       at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1322)
       at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7438)
       at android.app.ActivityThread.-$$Nest$mhandleBindApplication(unavailable)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2421)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:222)
       at android.os.Looper.loop(Looper.java:314)
       at android.app.ActivityThread.main(ActivityThread.java:8661)
       at java.lang.reflect.Method.invoke(Native method)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:565)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1081)

AndroidX Dependencies

If your app includes any AndroidX libraries, please list them here, along with the version info:

androidxCore = "1.10.1"
androidxLifecycle = "2.4.1"
androidxWorkManager = "2.8.1"
androidxNavigation = "2.5.2"
androidxStartupRuntime = "1.1.0"
androidxDatastore = "1.0.0"

Third-Party Library Dependencies

If your app includes any third-party libraries, please list them here, along with the version info:

• NA

[mukeshk-ms]

@singh-srikant can you please try to upgrade to latest SDK version 11.0.0 and see if the issue persists?
Additionally, please share the company portal logs (incident id) after enabling verbose logging in company portal app for further investigation.

[singh-srikant]

@mukeshk-ms Is this a known issue which has now been fixed in the SDK version 11.0.0 ? What could be the reason for the spike with the SDK version 10.4.1 ?

[mukeshk-ms]

@singh-srikant We generally want customers to use the latest SDK version. As requested earlier, for investigation of this issue please share the company portal logs (incident id) after enabling verbose logging in company portal app from one of the affected devices.