I'm trying to test out AppConfig app restrictions in BlackBerry UEM with Android, and I believe have i have uploaded the .apk correctly and applied the app configuration. This issue is, that I am not able to install the app on the device.
I've installed the UEM client, allowed it to setup an Android Work profile (i can see the orange briefcase symbols) and I can see the app I wish to install in the Assigned Work Apps, and i can tap "Free" (install) which sends a notification. Tapping the notification to install opens the UEM client the it shows:
Uable to perform action
You do not have permission to perform this action. Contact your organisation's IT administrator for more information.
Can anyone advise what I may be doing wrong?
If I setup the profile for a non-work profile, I am able to install the app, but the app configurations are not applied as it only appears to work in the work profile.
I think you are seeing the correct behaviour. Assuming you are referring to AppConfig.org style configuration, per the spec this requires the device to be managed. For Android, this also requires the APK to be hosted on Google Play. You can create a Google Play listing that is private to your organization, but the APK must reside on Google Play and not UEM for AppConfig.org to work (UEM gets the configuration template from Google Play).
The BlackBerry UEM app store is intended to be used on non managed devices (no Android Enterprise).
If you are creating a BlackBerry Dynamics app, you can use BlackBerry Dynamics specific app configuration, which does not require device management. I recommend reading these two blog articles for more information.
Should You Use BlackBerry Dynamics App Configuration or AppConfig?
Deploying Applications into Android for Work Using BES12 (older article, but still applies to UEM)
I now have a better understanding of what is going on now, in terms of BB app configurations and Android for Work app config.
I've implemented the GDStateListener on our startup activity, in which onAuthorize is triggered and our policy is consumed correctly.
The only remaining issue is that any subsequent activity launched from the startup activity is immediatlely closed with Activity.RESULT_CANCELED. The opening of subsequent activities works outside of the BB UEM environment, so perhaps there is something else I've missed?
I managed to get it all working.
Thank you for your support.