Every time I upload new watchface, I create 2 track in production.
1)watchface - production(Wear OS) - 10000001(1.0.0)
2)companion app - production - 2(1.1)
If I have change for the watchface, should I create new release for watchface track only or I need to create new release for both watchface and companion app?
Yesterday, my updated app was rejected. (I only create new release for watchface track.)
But I don’t know why it rejected due to missing scrollbar.
It just simple watchface, no scrollbar, the companion also simple app with 1 image and a button.
I am thinking to submit again. Increase both version number and create new release for both and send for review again.
Is this correct way?
Every time we update watchface, we need to create new release for both watchface and companion app?
Or what is the correct step to update watchface in google play?
which watch face studio version are you using to make watch face. I don’t think its due to update version. The error message shows that the previous version will remain visible and available to users only new update was rejected. so its not the versions
I have been updating both companion app versions and WF both andmostly no issues.BUT i have also updated few watchfaces with only updating the WF. since both phone companion app and WF have now separate release tracks its not required to update both. I
have made new companion app thanks to Bredlx who shared his source code for companion app So I have been updating both tracks for last 14 watchfaces updated in last 14 days.
in last 3 years i have faces some really irrational issues being raised by wear os team. At time there is ncompetentence from Google Testing Wear OS who will reject watchface for stupid reasons which are not even present. Opening dispute on rejections doesnt help much. i have found even when i updated same wf with 0
changes and just re built and sent again and it passed. Best is you try updating WF again
I updated in this manner already published watchfaces made in older WFS with latest WFS in this way .
a. if its 1.00(1) for the watchface aab then i update with version 1.01(2) and then 1.0.2(3) and so on.
b if its companion app i give 1st version number 1000 then 1001,1002 in Android Studio.
it doesnt matter even if you dont keep it 1000 or even 1 or 2 for companion app because since last year both tracks are separated .
Try updating again make a minor change and send it again for approval. You can also contact Google Play Console Help tonfurthet investigate what is they want try to get hold of them via live chat in their available timings or via email to know what issue they see.
Just sharing, one of app was suspended. Google keep rejected and mention its “Long description” issue. But all my watchface use almost the same description. So I do minor change in description n submit. After few times, the app was suspended and I got 1 bad record count for my developer account.
I wish I know the Google Play Console Help early
Recently, I create again the same watchface with new name, everything els the same, this time magically it approved. lol
yes you did it right to upload again as a different watchface. I would 1st try an update like i mentioned and if they reject it again then open issue via google play console help and chat with them online or send email .
I believe there are some non competent people in Google Wear OS Team who dont know either how to do their job. or it is there faulty automated approval system.which behaves like this.
