Closed Durzan666 closed 2 years ago
@Durzan666 can full logs be provided from the start of installation of io.simplifier.client
on the pixel running 10?
Hi,
I'm answering on behalf of @Durzan666. Prior to generating the following logs, I've factory resetted the device and applied my own accounts to the android system and company portal app. All other settings should be the same and I'm getting the same error.
@Ponsen Strange, it appears that the system is killing the Company Portal process immediately after your app starts up and the MAM SDK is unable to re-establish communication with it. Could you reproduce the issue again and follow the directions at https://docs.microsoft.com/en-us/mem/intune/user-help/send-logs-to-microsoft-android to upload logs? Please relay the incident ID here and we can take a look.
These error messages and the FileNotFoundException
stack below are a bit concerning, but unclear if they're related. Does this issue reproduce if you do not install with Android Studio?
2022-03-03 12:54:46.743 12432-12432/? E/studio.deploy: Could not get package user id: /system/bin/run-as: unknown package: io.simplifier.client
2022-03-03 12:54:46.784 12432-12432/? E/studio.deploy: Could not find apks for this package: io.simplifier.client
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: java.io.FileNotFoundException: /jacoco.exec: open failed: EROFS (Read-only file system)
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: at libcore.io.IoBridge.open(IoBridge.java:496)
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: at java.io.FileOutputStream.<init>(FileOutputStream.java:235)
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: at org.jacoco.agent.rt.internal_8ff85ea.output.FileOutput.openFile(FileOutput.java:67)
2022-03-03 12:54:53.856 10576-10747/? W/DeviceAppInfoWork: missing version info.
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: at org.jacoco.agent.rt.internal_8ff85ea.output.FileOutput.startup(FileOutput.java:49)
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: at org.jacoco.agent.rt.internal_8ff85ea.Agent.startup(Agent.java:122)
2022-03-03 12:54:53.856 12594-12594/io.simplifier.client W/System.err: at org.jacoco.agent.rt.internal_8ff85ea.Agent.getInstance(Agent.java:50)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at org.jacoco.agent.rt.internal_8ff85ea.Offline.<clinit>(Offline.java:31)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at org.jacoco.agent.rt.internal_8ff85ea.Offline.getProbes(Offline.java:51)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at io.simplifier.customLauncher.SimplifierApplication.$jacocoInit(Unknown Source:13)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at io.simplifier.customLauncher.SimplifierApplication.<clinit>(Unknown Source:0)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at java.lang.Class.newInstance(Native Method)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:76)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at androidx.core.app.CoreComponentFactory.instantiateApplication(CoreComponentFactory.java:52)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at android.app.Instrumentation.newApplication(Instrumentation.java:1155)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at android.app.LoadedApk.makeApplication(LoadedApk.java:1218)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6431)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at android.app.ActivityThread.access$1300(ActivityThread.java:219)
2022-03-03 12:54:53.857 12594-12594/io.simplifier.client W/System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1859)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at android.os.Handler.dispatchMessage(Handler.java:107)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at android.os.Looper.loop(Looper.java:214)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at android.app.ActivityThread.main(ActivityThread.java:7356)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at java.lang.reflect.Method.invoke(Native Method)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: Caused by: android.system.ErrnoException: open failed: EROFS (Read-only file system)
2022-03-03 12:54:53.858 12594-12594/io.simplifier.client W/System.err: at libcore.io.Linux.open(Native Method)
2022-03-03 12:54:53.859 12594-12594/io.simplifier.client W/System.err: at libcore.io.ForwardingOs.open(ForwardingOs.java:167)
2022-03-03 12:54:53.859 12594-12594/io.simplifier.client W/System.err: at libcore.io.BlockGuardOs.open(BlockGuardOs.java:252)
2022-03-03 12:54:53.859 12594-12594/io.simplifier.client W/System.err: at libcore.io.ForwardingOs.open(ForwardingOs.java:167)
2022-03-03 12:54:53.859 12594-12594/io.simplifier.client W/System.err: at android.app.ActivityThread$AndroidOs.open(ActivityThread.java:7255)
2022-03-03 12:54:53.859 12594-12594/io.simplifier.client W/System.err: at libcore.io.IoBridge.open(IoBridge.java:482)
2022-03-03 12:54:53.859 12594-12594/io.simplifier.client W/System.err: ... 23 more
@bannus Logs are uploaded. The incident ID is
NMWK7DDZ
@Ponsen Apologies, could you try that again? That incident didn't contain any files.
@bannus I exported the logs on the affected device to the local storage and they keep beeing 0 bytes. Today I've had a call with the support [Case #:29854779], shared my screen and sent several screenshots and logs. Hopefully I'll have some feedback from them later.
@Ponsen did you receive the help necessary from support / have any updates to share?
@Durzan666 / @Ponsen are you still experiencing this issue? Could you clarify whether other apps (e.g. Outlook) on the same device are able to receive MAM policy and only your app is not? Or are all apps on the device experiencing the same problem?
@joakley-msft Yes, we will still experience this issue. The Microsoft Premier Support told us after several calls that they can't help us and we shall write a mail to msintuneappsdk@microsoft.com
Closing as we've been unable to reproduce or receive logs from an affected device. Please re-open if log collection succeeds, and let us know whether all apps on the device are experiencing the same problem, or if other apps (e.g. Outlook) on the same device are able to receive MAM policy and only your app is affected.
Updated to 9.0.0. Still same issue, but successfully generated logs. IncidentID: 7YQ7PJNB Also sent a mail to msintuneappsdk@microsoft.com containing a few more issues and the logs.
Describe the bug: We integrated the SDK but the automatic enrollment doesn't work although the Intune Company App is installed and the user is signed in. Only one of our devices (Google Pixel 5 with Android 12) doesn't show the issue. All our devices are BYOD devices.
To Reproduce Steps to reproduce the behavior:
Expected behavior: Popup stating the enrollment was successful.
Screenshots and logs:
Logs of not working device Google Pixel (Android 10)
Logs of working device Google Pixel 5 (Android 12)
Smartphone (please complete the following information):
Intune App SDK for Android (please complete the following information):