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.
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.
Hi Michael
Today passed the Google review and was published our new release (better say 'hotfix') where we changed the version codes schema, in a way which you offered.
The MDM configuration, and the "This app offers managed configuration" label re-appears on the Managed Play Console.
Many thanks to you!
We couldn't imagine this reason.
Contacting the Play Console support was useless, they only pointed to the, let's say 'noob' Hep pages which indeed doesn't covers this case.
Only your help solved this puzzle.
