My question might seem really stupid, to those who have worked on android Airwatch implementation. But their documentation is not very well written, and I have a few doubts.
So I have setup my user, and added my device using airwatch console.
I have added the App restrictions code in my existing android application.
I have also added the key, values to be pushed to application, via Airwatch Agent app.
But I do not receive these key, values, which I should when I execute the following code :
Bundle appRestrictions = myRestrictionsMgr.getApplicationRestrictions();
The appRestrictions bundle is empty.
I read some where in the docs, that the AppConfig requires Android 5.0+ with Android for Work Device. Does this mean I have to enable android for work capability on my android device? Is this required even for development purpose? I tried in vain doing so using this link : https://support.google.com/a/answer/6178111?hl=en. Can some one please share a doc, to enable android for work capability on my android device, if this is required.
The product supports Apple iOS, Google Android and Chrome OS, BlackBerry QNX and Samsung Tizen. It supports MDM on Apple macOS and Windows 10, as well. A managed cloud-based MDM service, AirWatch Express, is also available.
The Workspace ONE SDK (formerly known as AirWatch SDK) code library for Google Android devices can be used to enable additional app config and security capabilities that may not yet be available natively as part of the AppConfig Community.
You will indeed need Android for Work in order to use Airwatch to configure your application.
You should ensure you are using a device that supports AfW. All devices with Android 6.0+ support work profiles, as well as many devices with Android 5.0+. Some recommended devices can be found here
Once you have done so, you should create a new Profile in the Airwatch console that ensure that they will create a work profile on your device. Go to Devices >> Profiles >> List View and Click on "Add" >> "Add Profile" and choose "Android" >> "Android for Work"
This should allow you to create an AfW policy that will apply to any assigned groups. Any apps you push to these devices can be configured using the App Restrictions framework by editing an application, going to the "Deployment" tab and enabling "Send Application Configuration". You should be able to set the key value pairs from there.
All that being said, if you are testing from a development perspective, you are much better off testing with TestDPC, an open source testing tool Google makes available in Google Play (just search for "TestDPC") and on Github
There is a user guide on github, but it is very easy to use for creating work profiles, setting app configurations using app restrictions and more.
I would use Airwatch once you are ready to do production testing, but TestDPC is a much better tool while you are still developing.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With