Forum Discussion
MDM configuration became lost
Hi VKuts,
Thank you for your patience while we have been investigating this issue.
Our engineers believe this may be caused by a Wear OS variant of your app having a higher version number than your mobile variant in Google Play.
By default Google Play removes MCM from non-mobile applications (Wear/TV). We are working on a way to prevent MCM from being removed from this specific app in the future and I will confirm back here when that has been completed.
In the meantime if you publish your mobile app with a higher version than the Wear variant it will likely resolve this issue.
Let me know if this helps.
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.
