Forum Discussion
MDM configuration became lost
- 28 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.
Lizzie I will be very grateful to you, if you can take a look.
I compared the app's manifest and managed config XML ten times.
In the project sources and in the APK binaries, downloaded from the Google Play console.
Nothing bad was found.
The only difference between previous 14.2.1 and actual 15.0.0 releases, regarding to managed config, was removed one bool parameter. I can't believe that it was an origin of trouble.
Thank you in advance!
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.
- VKuts28 days agoLevel 1.6: Donut
Hi Michael
Woooow, this could be true.
Indeed, in the recent release the Wear companion app was included. Because it's a companion (non-standalone) wearable app, according to Google standalone-apps guide, it was made as variant.
I followed the Google multiple-apks#VersionCodes guide, when modified the version numbers scheme. Of course, because the Android app is far more important, it got the version number 01, and the wear app got the number 02. Everything exactly as you pointed.
In all these and related guides I haven't seen any notice or warning about MDM configurations.I'll update the versions scheme in our upcoming hotfix, to be sure that Android app has the higher version number than it's wearable companion. Many thanks you for the possible solution. And sure, I will let you know.
- VKuts22 days agoLevel 1.6: Donut
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.
Related Content
- 9 months ago
- 2 months ago