Forum Discussion
MDM configuration became lost
- 21 days ago
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.
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
Related Content
- 9 months ago
- 2 months ago