E-N-G-XOR
commented
5 months ago align_log.txt [Uploading wrap_log.txt…]()
ATTACHMENTS
Open E-N-G-XOR opened 5 months ago
E-N-G-XOR
commented
5 months ago align_log.txt [Uploading wrap_log.txt…]()
ATTACHMENTS
E-N-G-XOR
commented
5 months ago more attachments!
FAngelvs
commented
5 months ago Not sure if this is related, but we have something similar with our Intune Wrapped app. It is Cordova based app, fails at start. Place is different, but looks like something goes very wrong with it once wrapped. Similar behavior reported by other developers too.
Some more details here: https://issuetracker.google.com/issues/316396709
Our latest update is that it now fails on start and can be started later with no issues. Previously, it would start failing after some time and it was enough to clear cache to get it working for a while again. We have changed Intune policy to have minimum possible restrictions.
For us, this started to happen suddenly on an app that was OK, no new releases issued. Issue happens randomly, no idea how to reproduce it. As for now, it looks like app works fine if not wrapped. On devices that we have seen crash every day, it works for a week or two now, no issues reported.
mcsimons
commented
5 months ago Hi @E-N-G-XOR, thanks for the report. Is this your first time wrapping your app or did this ever work previously?
From the logs provided it looks like the crash in caused Android's foreground service launch restrictions, https://developer.android.com/about/versions/12/behavior-changes-12#foreground-service-launch-restrictions
01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: CAUSED BY: ANDROID.APP.FOREGROUNDSERVICESTARTNOTALLOWEDEXCEPTION: STARTFOREGROUNDSERVICE() NOT ALLOWED DUE TO MALLOWSTARTFOREGROUND FALSE: SERVICE AERO.INFORM.UXWRAPPER.FX.SC.APPNAME/AERO.INFORM.ANDROID.BACKGROUND.GSBACKGROUNDSERVICE 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.APP.FOREGROUNDSERVICESTARTNOTALLOWEDEXCEPTION$1.CREATEFROMPARCEL(FOREGROUNDSERVICESTARTNOTALLOWEDEXCEPTION.JAVA:54) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.APP.FOREGROUNDSERVICESTARTNOTALLOWEDEXCEPTION$1.CREATEFROMPARCEL(FOREGROUNDSERVICESTARTNOTALLOWEDEXCEPTION.JAVA:50) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.OS.PARCEL.READPARCELABLEINTERNAL(PARCEL.JAVA:4882) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.OS.PARCEL.READPARCELABLE(PARCEL.JAVA:4864) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.OS.PARCEL.CREATEEXCEPTIONORNULL(PARCEL.JAVA:3064) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.OS.PARCEL.CREATEEXCEPTION(PARCEL.JAVA:3053) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.OS.PARCEL.READEXCEPTION(PARCEL.JAVA:3036) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.OS.PARCEL.READEXCEPTION(PARCEL.JAVA:2978) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.APP.IACTIVITYMANAGER$STUB$PROXY.STARTSERVICE(IACTIVITYMANAGER.JAVA:6437) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.APP.CONTEXTIMPL.STARTSERVICECOMMON(CONTEXTIMPL.JAVA:2002) 01-23 16:48:22.909 31689 31689 E ANDROIDRUNTIME: AT ANDROID.APP.CONTEXTIMPL.STARTFOREGROUNDSERVICE(CONTEXTIMPL.JAVA:1967)
Is "AERO.INFORM.UXWRAPPER.FX.SC.APPNAME/AERO.INFORM.ANDROID.BACKGROUND.GSBACKGROUNDSERVICE" a service in your application? If so, you may want to check that the service you are trying to start adheres to Android's restrictions.
leoslima13
commented
4 months ago This is also happening with my .net MAUI version. After Portal Company Required notification, and user clicks on Go To Store to install, after install the application will restart. But it crashes right after accessing the MSAL library. But when the application is opened again, it prompts the Android Activity showing all the requirements to use the application and its not crashing anymore. I think is something missing during this process when the policies will be applied and the application was alive before
Questions to Ask Before Submission
Does you app launch successfully without wrapping? YES
Have you reviewed the prerequisites for App Wrapping? YES
Does your issue have a solution in the Troubleshooting Guide? NOPE, WISH IT DID!
Have you checked the Microsoft Intune App SDK for Android repository for similar issues? YES, BUT, WE DON'T HAVE SDK INTEGRATION ON OUR APP.
APK Crashing post Intune wrapping · Issue msintuneappsdk/intune-app-wrapping-tool-android#99 · msintuneappsdk/ms-intune-app-sdk-android (github.com)
Describe the bug: A clear and concise description of what the bug is.
THE INTUNE WRAPPING COMPLETES, BUT WILL NOT LAUNCH ON THE DEVICE.
To Reproduce Steps to reproduce the behavior:
SIMPLY, GO TO APPS AND TRY TO LAUNCH THE APP. IT WILL IMMEDIATELY CRASH.
CAUSE: NULL POINTER DEREFERENCE
Expected behavior: A clear and concise description of what you expected to happen.
THE APP SHOULD LAUNCH AND ASK TO LOGIN
Screenshots and logs:
DEVICE SCREENSHOT ATTACHED AND
If your app is crashing post-wrapping, do you have app logs for the crash itself? YES, SNIPLET ABOVE AND THE FULL LOG
If your app is crashing pre-wrapping, do you have app logs for the wrapper errors? NO CRASH BEFORE WRAPPING
Smartphone (please complete the following information):
Intune app wrapping tool (please complete the following information):
VERSION - COMMENTS
2528.3 - WRAPS FAILS WITH API VERSION ERROR (ATTACHED) 2896.3 - WRAPS FAILS WITH API VERSION ERROR (ATTACHED) 3199.5 - WRAPS FAILS WITH API VERSION ERROR (ATTACHED) 3401.4 - WRAPS FAILS WITH API VERSION ERROR (ATTACHED) 3610.6 - WRAPS FAILS WITH API VERSION ERROR (ATTACHED) 3935.1 - WRAP FAILS WITH NO APK FILE GENERATED 4191.6 - WRAPS BUT WILL NOT LAUNCH ON DEVICE 4214.3 - WRAPS BUT WILL NOT LAUNCH ON DEVICE
JAVA/KOTLIN PACKAGE
For pre-wrapping errors, does the app build without being wrapped? YES INSTALLS AND WORKS FINE
For post-wrapping errors, does the app launch without being wrapped? YES,
Who is the customer? INTERNAL USERS WITH OWN DEVICES....
Do you see a trend with it only being reproduced on a specific device? IT IS HAPPENING WITH ALL THE DEVICES WE HAVE TESTED, INCLUDING NOTE 22 WITH LATEST ANDROID. NO, TRIED SEVERAL DEVICES, BUT PRIMARIALLY ON SAMSUNG NOTE 22 ULTRA
Additional context: Add any other context about the problem here.