Outlook and MSLauncher crashing if intune is also installed on a x86/x86_64 Android 11 device

%3CLINGO-SUB%20id%3D%22lingo-sub-2247676%22%20slang%3D%22en-US%22%3EOutlook%20and%20MSLauncher%20crashing%20if%20intune%20is%20also%20installed%20on%20a%20x86%2Fx86_64%20Android%2011%20device%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2247676%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20running%20into%20an%20issue%20with%20Intune%20and%20Android%2011%20on%20our%20x86_64%20devices.%20The%20devices%20are%20still%20in%20test%20but%20issue%20was%20also%20reproduced%20on%20a%20chromebook.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMore%20specifically%2C%20if%20Intune%20is%20installed%20along%20with%20Outlook%20or%20Microsoft%20launcher%2C%20then%20both%20these%20apps%20crash%20upon%20launch%20on%20Android%2011%20x86_64.%20Without%20Intune%2C%20they%20work%20fine.%20You%20just%20have%20to%20install%20Intune%20%E2%80%A6don%E2%80%99t%20need%20to%20register%20the%20device%20or%20anything%20to%20get%20the%20crash.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20devices%20are%20x86_64%20based%20and%20when%20we%20install%20Microsoft%20launcher%2FOutlook%2C%20we%20get%20an%20ARM%20version%20of%20the%20app%20from%20playstore.%20The%20ARM%20emulator(%20houdini%20)%20in%20our%20device%20makes%20this%20work.%20But%20with%20Intune%20also%20installed%2C%20they%20crash.%20Without%20Intune%2C%20they%20work%20fine%20on%20our%20Android%2011%20x86_64%20device%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20apps%20where%20playstore%20gives%20us%20a%20x86_64%2F86%20version%20of%20the%20app%2C%20they%20work%20fine%20with%20intune.%20word%2Fexcel%2Fteams%20etc%20all%20work%20fine%20with%20intune%20on%20our%20Android%2011%20x86_64%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20reproduce%20the%20problem%20on%20a%20Chromebook%20(%20HP%20Chromebook%20x360%20)%20if%20the%20underling%20android%20image%20it%20uses%20is%20Android%2011%20to%20run%20android%20apps%E2%80%A6.so%20it%20is%20not%20just%20our%20device%20showing%20this%20issue.%20I%20believe%20any%20x86_64%2Fx86%20based%20Android%20device%20will%20show%20this%20issue%20on%20Android%2011%20with%20the%20ARM%20emulator.%20Following%20is%20the%20crash%20from%20adb%20log.%20Please%20note%20that%20device%20encryption%20is%20enabled%20and%20other%20apps%20like%20word%2Fteams%2Fexcel%20do%20not%20show%20this%20issue.%20Only%20arm%20based%20apps%20(%20outlook%2Fmslauncher%20)%20are%20showing%20this%20issue.%20I%20also%20do%20not%20understand%20why%20playstore%20is%20giving%20us%20arm%20version%20of%20outlook%20when%20an%20x86_64%20version%20is%20also%20available.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20would%20like%20to%20mention%20that%20this%20issue%20is%20not%20seen%20on%20a%20Android%209%20x86_64%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20D%20AndroidRuntime%3A%20Shutting%20down%20VM%3C%2FP%3E%3CP%3E%3CEM%3E2%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20FATAL%20EXCEPTION%3A%20main%3C%2FP%3E%3CP%3E%3CEM%3E3%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20Process%3A%20com.microsoft.launcher%2C%20PID%3A%202057%3C%2FP%3E%3CP%3E%3CEM%3E4%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20java.lang.RuntimeException%3A%20Unable%20to%20instantiate%20application%20com.microsoft.launcher.LauncherApplication%3A%20java.lang.IllegalStateException%3A%20MAM%20was%20unable%20to%20initialize%20file%20encryption%20with%20error%200x3a1540200000026%3C%2FP%3E%3CP%3E%3CEM%3E5%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20android.app.LoadedApk.makeApplication(LoadedApk.java%3A1268)%3C%2FP%3E%3CP%3E%3CEM%3E6%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20android.app.ActivityThread.handleBindApplication(ActivityThread.java%3A6686)%3C%2FP%3E%3CP%3E%3CEM%3E7%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20android.app.ActivityThread.access%241300(ActivityThread.java%3A237)%3C%2FP%3E%3CP%3E%3CEM%3E8%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20android.app.ActivityThread%24H.handleMessage(ActivityThread.java%3A1913)%3C%2FP%3E%3CP%3E%3CEM%3E9%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%20at%20android.os.Handler.dispatchMessage(Handler.java%3A106)%3C%2FP%3E%3CP%3E%3CEM%3E10%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20android.os.Looper.loop(Looper.java%3A223)%3C%2FP%3E%3CP%3E%3CEM%3E11%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20android.app.ActivityThread.main(ActivityThread.java%3A7660)%3C%2FP%3E%3CP%3E%3CEM%3E12%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20java.lang.reflect.Method.invoke(Native%20Method)%3C%2FP%3E%3CP%3E%3CEM%3E13%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.android.internal.os.RuntimeInit%24MethodAndArgsCaller.run(RuntimeInit.java%3A592)%3C%2FP%3E%3CP%3E%3CEM%3E14%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.android.internal.os.ZygoteInit.main(ZygoteInit.java%3A947)%3C%2FP%3E%3CP%3E%3CEM%3E15%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20Caused%20by%3A%20java.lang.IllegalStateException%3A%20MAM%20was%20unable%20to%20initialize%20file%20encryption%20with%20error%200x3a1540200000026%3C%2FP%3E%3CP%3E%3CEM%3E16%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.microsoft.intune.mam.client.ipcclient.MAMClientImpl.initialize(MAMClientImpl.java%3A285)%3C%2FP%3E%3CP%3E%3CEM%3E17%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.microsoft.intune.mam.client.ipcclient.MAMClientSingletonImpl.ensureInitialized(MAMClientSingletonImpl.java%3A74)%3C%2FP%3E%3CP%3E%3CEM%3E18%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.microsoft.intune.mam.client.app.ApplicationBehaviorImpl.attachBaseContext(ApplicationBehaviorImpl.java%3A115)%3C%2FP%3E%3CP%3E%3CEM%3E19%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20java.lang.reflect.Method.invoke(Native%20Method)%3C%2FP%3E%3CP%3E%3CEM%3E20%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.microsoft.intune.mam.InterProxy%24InterInvocationHandler.invoke(InterProxy.java%3A88)%3C%2FP%3E%3CP%3E%3CEM%3E21%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20java.lang.reflect.Proxy.invoke(Proxy.java%3A1006)%3C%2FP%3E%3CP%3E%3CEM%3E22%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20%24Proxy6.attachBaseContext(Unknown%20Source)%3C%2FP%3E%3CP%3E%3CEM%3E23%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.microsoft.intune.mam.client.app.MAMApplication.attachBaseContext(%3A11)%3C%2FP%3E%3CP%3E%3CEM%3E24%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20androidx.multidex.MultiDexApplication.attachBaseContext(%3A1)%3C%2FP%3E%3CP%3E%3CEM%3E25%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20com.microsoft.launcher.LauncherApplication.attachBaseContext(%3A2)%3C%2FP%3E%3CP%3E%3CEM%3E26%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20android.app.Application.attach(Application.java%3A351)%3C%2FP%3E%3CP%3E%3CEM%3E27%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20android.app.Instrumentation.newApplication(Instrumentation.java%3A1159)%3C%2FP%3E%3CP%3E%3CEM%3E28%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20at%20android.app.LoadedApk.makeApplication(LoadedApk.java%3A1260)%3C%2FP%3E%3CP%3E%3CEM%3E29%3C%2FEM%3E03-31%2011%3A48%3A17.937%26nbsp%3B%202057%26nbsp%3B%202057%20E%20AndroidRuntime%3A%20%26nbsp%3B%26nbsp%3B%20...%209%20more%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2247676%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAndroid%2011%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehoudini%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ex86_64%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

We are running into an issue with Intune and Android 11 on our x86_64 devices. The devices are still in test but issue was also reproduced on a chromebook.

 

More specifically, if Intune is installed along with Outlook or Microsoft launcher, then both these apps crash upon launch on Android 11 x86_64. Without Intune, they work fine. You just have to install Intune …don’t need to register the device or anything to get the crash.

 

Our devices are x86_64 based and when we install Microsoft launcher/Outlook, we get an ARM version of the app from playstore. The ARM emulator( houdini ) in our device makes this work. But with Intune also installed, they crash. Without Intune, they work fine on our Android 11 x86_64 device

 

For apps where playstore gives us a x86_64/86 version of the app, they work fine with intune. word/excel/teams etc all work fine with intune on our Android 11 x86_64 device.

 

I have also reproduce the problem on a Chromebook ( HP Chromebook x360 ) if the underlying android image it uses is Android 11 to run android apps….so it is not just our device showing this issue. I believe any x86_64/x86 based Android device will show this issue on Android 11 with the ARM emulator. Following is the crash from adb log. Please note that device encryption is enabled and other apps like word/teams/excel do not show this issue. Only arm based apps ( outlook/mslauncher ) are showing this issue. I also do not understand why playstore is giving us arm version of outlook when an x86_64 version is also available.

 

Also would like to mention that this issue is not seen on a Android 9 x86_64 device.

 

03-31 11:48:17.937  2057  2057 D AndroidRuntime: Shutting down VM

203-31 11:48:17.937  2057  2057 E AndroidRuntime: FATAL EXCEPTION: main

303-31 11:48:17.937  2057  2057 E AndroidRuntime: Process: com.microsoft.launcher, PID: 2057

403-31 11:48:17.937  2057  2057 E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate application com.microsoft.launcher.LauncherApplication: java.lang.IllegalStateException: MAM was unable to initialize file encryption with error 0x3a1540200000026

503-31 11:48:17.937  2057  2057 E AndroidRuntime:     at android.app.LoadedApk.makeApplication(LoadedApk.java:1268)

603-31 11:48:17.937  2057  2057 E AndroidRuntime:     at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6686)

703-31 11:48:17.937  2057  2057 E AndroidRuntime:     at android.app.ActivityThread.access$1300(ActivityThread.java:237)

803-31 11:48:17.937  2057  2057 E AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)

903-31 11:48:17.937  2057  2057 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:106)

1003-31 11:48:17.937  2057  2057 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:223)

1103-31 11:48:17.937  2057  2057 E AndroidRuntime:    at android.app.ActivityThread.main(ActivityThread.java:7660)

1203-31 11:48:17.937  2057  2057 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)

1303-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)

1403-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

1503-31 11:48:17.937  2057  2057 E AndroidRuntime: Caused by: java.lang.IllegalStateException: MAM was unable to initialize file encryption with error 0x3a1540200000026

1603-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.microsoft.intune.mam.client.ipcclient.MAMClientImpl.initialize(MAMClientImpl.java:285)

1703-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.microsoft.intune.mam.client.ipcclient.MAMClientSingletonImpl.ensureInitialized(MAMClientSingletonImpl.java:74)

1803-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.microsoft.intune.mam.client.app.ApplicationBehaviorImpl.attachBaseContext(ApplicationBehaviorImpl.java:115)

1903-31 11:48:17.937  2057  2057 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)

2003-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.microsoft.intune.mam.InterProxy$InterInvocationHandler.invoke(InterProxy.java:88)

2103-31 11:48:17.937  2057  2057 E AndroidRuntime:    at java.lang.reflect.Proxy.invoke(Proxy.java:1006)

2203-31 11:48:17.937  2057  2057 E AndroidRuntime:    at $Proxy6.attachBaseContext(Unknown Source)

2303-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.microsoft.intune.mam.client.app.MAMApplication.attachBaseContext(:11)

2403-31 11:48:17.937  2057  2057 E AndroidRuntime:    at androidx.multidex.MultiDexApplication.attachBaseContext(:1)

2503-31 11:48:17.937  2057  2057 E AndroidRuntime:    at com.microsoft.launcher.LauncherApplication.attachBaseContext(:2)

2603-31 11:48:17.937  2057  2057 E AndroidRuntime:    at android.app.Application.attach(Application.java:351)

2703-31 11:48:17.937  2057  2057 E AndroidRuntime:    at android.app.Instrumentation.newApplication(Instrumentation.java:1159)

2803-31 11:48:17.937  2057  2057 E AndroidRuntime:    at android.app.LoadedApk.makeApplication(LoadedApk.java:1260)

2903-31 11:48:17.937  2057  2057 E AndroidRuntime:    ... 9 more

 

1 Reply

As of july 9, 2021, a new outlook has been released on playstore with version 4.2125.2

Now, we are getting the correct outlook installed on x86_64 devices where the .so files in the outlook app are compiled for x86_64. Outlook on x86_64 now works and no longer crashes if intune is also installed.

The problem is now only with MSLauncher.