Forum Discussion
MDM configuration became lost
A few years ago we added an MDM configuration to our app, according to the straightforward guide Setup managed configuration
Previous month we released a new 15.0.0 version of our app, IQ SmartApp Enterprise
Besides other changes, in this release we removed one option from the MDM configuration XML, a deprecated boolean parameter. Indeed the XML validity wasn't broken, no related changes in the app Manifest or so on.
However our customers started to complain, that app lost the ability to configure MDM parameters. Also, when adding the app to Approved list on MDM Solutions (we checked on HMD and TinyMDM), in the app details was lost a badge "Tis app offers managed configuration".
If download AAB and/or APK from Google Play Console and unpack them, or open them in Android Studio, the required Android Manifest parameter "android.content.APP_RESTRICTIONS" is present and pints to MDM XML config file which is also present in the AAB or APK.
If check the APK, taken from Google Play Console, locally with TestDPC app, the managed configuration is also present.
Can you please help to understand, what's going on? As for me, removing one of the MDM parameter from the managed configuration config shouldn't be a reason of disappearing the whole managed configuration. Which is actually present in the AAB or APK builds.
5 Replies
This would be something to investigate on the Google Play side, but there is probably an issue with your managed configuration declaration, I would double check it to make sure it matches Google requirements
This would be something to investigate on the Google Play side, but there is probably an issue with your managed configuration declaration, I would double check it to make sure it matches Google requirements
Hi Jeremy,
Thanks to your attention to the issue.
Sure, please do that check, I'm appreciate you.
As I can get, there is a predefined tag in the app's Manifest, named android.content.APP_RESTRICTIONS. Which must refer to the MDM config XML file, which format is clearly described in the Google guide. IMO it's enough to make a decision, whether an app has or hasn't the managed configuration.
Our team already checked this probably ten times, but indeed another check would be great.
I contacted the Google Play support. Unfortunately I got a bureaucratic answer. In short, asking their support was completely useless.
I have looked at the manifest.xml and managed_configuration.xml of the app.
In the manifest, android.content.APP_RESTRICTIONS is in the right place, references the XML and has no spelling or syntax errors.
The syntax of the three configurations in the managed_configuration.xml also seems correct to me. Mandatory attributes such as key, title and restrictionType are defined for each restriction. I am not a developer, but based on the xml data I would say that it should work like this.The MGP link can be used to verify that the managed configuration is not recognized: https://play.google.com/work/apps/details?id=com.iqm.enterprise.smartapp
Lizzie Can you take a look at this? It looks similar to the Gboard problem to me.
