Really could use some guidance on how to debug / troubleshoot this issue I'm having.
I built my first app designed to be configured by an Enterprise MDM / EMM service. I created the app_restrictions.xml file, and I setup my Bundle for restrictions to be read in from that file.
When running in debug on a device connected to my computer, I can successfully read in all the values from the XML file
However the problem occurs once I roll it into production.
I've published the app to the play store, and added the app to the EMM/MDM.
I can see the managed configuration settings all appear inside the EMM/MDM - so I've got everything right up to this point.
However once the app is pushed with an alternate configuration to a device, the values being read in are not the custom values from the EMM/MDM - they are my default values inside of the XML that I developed.
I cannot find any good resources on troubleshooting this part of the process.
Anyone done this before have any ideas?
I've been creating a lot of B2B applications lately, and providing the customer with the ability to customize the app on a per-device or per-deployment basis is critical.
Here's my guide to adding App Config settings into your application for any MDM to be able to leverage these via the Managed Google Play Store:
Manifest: you must have this inside the section:
app_restrictions.xml This file will hold your app restrictions. There are only a few options for app restrictions but you can make this work in all kinds of different creative ways. here's a basic set of restrictions:
For some of your restrictions you may want a pre-defined list of items in a drop down style selector - as shown above you can use an array for this and put the following into your Strings.xml
Strings.xml:
Now - loading these restrictions into your app:
To load them I created this loadRestrictions sample:
Enjoy!!!