-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INSTALL_FAILED_USER_RESTRICTED #35
Comments
Installation of non Google Play apps in the work side of Android Enterprise is disabled by default. It must be enabled in BlackBerry UEM.
Note that there are also some policy items to enable or disable debugging, which you may need to toggle to enabled as well in order to debug the app. |
The check is enabled for "Allow installation of non Google Play apps". |
Are you able to install the same APK from file storage? Copy the APK to the SD card and try to install from a file browser app installed on the work side. |
Yes I am able to install same APK from file storage |
Has the app been assigned to the user in BlackBerry UEM? Have a read through this old blog post I wrote way back in 2015 in regards to Samsung Knox and follow the steps there. Samsung has moved on from Knox and are using Android Enterprise now, but they have incorporated many Knox features into Android Enterprise on their devices to offer some enhanced security and control. Debugging with Samsung KNOX |
If you are still facing INSTALL_FAILED_USER_RESTRICTED issue try this this methods: |
Hi,
I have been using blackberry dynamics and UEM for my enterprise apps.
Previously I used android version 10. It worked perfectly for creating build for --user 10 on work profile . But when I updated my device to Samsung s10e with android version 11 or greater. It started giving error of INSTALL_FAILED_USER_RESTRICTED. And I am unable to install build on my work profile with android 11 and greater .
So please suggest me a work around so that I would be able to install my work tabs apps directly from android studio.
The text was updated successfully, but these errors were encountered: