-
Notifications
You must be signed in to change notification settings - Fork 11
Troubleshooting the App Wrapper
Repro Steps
- Successfully wrap app on PC #1.
- Wrap app on PC #2.
Expectation: App is wrapped successfully.
Observed Behavior: App fails to wrap successfully.
Resolution
Verify PC #2 is appropriately configured for app wrapping. See Fulfill the prerequisites for using the App Wrapping Tool for more details.
"There was a problem parsing app package", "App not installed as package appears to be invalid." or similar on App Installation
Repro Steps
- Successfully wrap app.
- Upload app to Intune.
- Push app to device.
- Launch app on device.
Expectation: App installs to the device successfully.
Observed Behavior: App fails to install and an error dialog stating "There was a problem parsing app package" appears.
Resolution
Confirm your app was properly zipaligned and signed after wrapping and prior to uploading to Intune.
While Google Play verifies signing prior to upload, Intune does not employ such a mechanism.
As a result, the app can be uploaded without proper signing, which results in an .apk that cannot be installed on the device.
Repro Steps
- Successfully wrap app.
- Launch app on device.
- Login with valid credentials.
Expectation: One authentication prompt appears and, once the user authenticates, is permitted access to the application.
Observed Behavior: An authentication prompt appears, the user authenticates, but is shown a second authentication prompt. Once the user authenticates for a second time they are permitted to access the application.
Resolution
This is a known and expected limitation of the App Wrapper. In our documentation for Reasons to use the App Wrapping Tool we explicitly state "Your app has minimal user authentication experiences." for this precise reason.
Your application may be better integrated fully with the Intune App SDK for Android.