Does any of you guys get rejections for your companion app with the following;
Your app contains content that isn’t compliant with the Broken Functionality policy.
It is the same companion app that has passed before for probably 10 faces recently, but all of a sudden I have about 5 faces with this issue.
I have not received any rejections like this on mine (yet), but I’ll bookmark this post and let you know if I do in the future. Since the message pointed it out specifically, have you double checked that all buttons in your app perform their intended action when installed on a real device? It looks like you’ve been doing watch face design for at least a few years now, so depending upon the functionality you have integrated into your companion app, it is possible that some newer Android devices do not react as expected to older code.
Have you checked that the companion app runs as expected on more than one real device? It is a really good idea to check on as many devices as possible, but make sure at least a few of those are real physical devices. If you only check using emulated devices, depending upon what you are testing you may not get a 100% accurate test result. Emulators are an amazing option for sure, but they are not perfect. If you don’t have access to more than one real device, I would suggest asking a friend or family member to install the app on their device(s) to help you test.
Hey, thank you for the reply.
Yes I test the code on my Fold 4 and also my wifes slightly older Flip. I use the companion app from Bredlix, as I am not a coder and just followed the instructoins on there.
It’s a simple app, has an install button, go to my page, leave a review and my privacy policy. Then the main button says install to device…
I winder if I should net release the watch face first, then a day later the companion app, maybe they can’t complete the tasks because the watch face is not out yet… I also wonder if these testers know they need to be connected to a watch to push the install command…
I don’t know, will try a couple of things, this google play story is so frustrating.
Remove go to your page button, leave review button, privacy policy button on your companion app will solve that problem. Open another page is not allowed as far your companion app not marked as “Contains Ads”.
Can @bredlix confirm this?
Hey!
I can definitely confirm that in my app there is a logic that can cuase this type of rejection. It is related to the main button being clickable without result on app open.
Unfortunately i wont be able to apply fixes in nearest 2-3 weeks.
Hey guys, thank you for the replies.
I have just had 3 watch faces approved, so I think it is just the luck of the draw and what tester you get on the day. Same Companion app as the other 2 that were rejected.
By the way, thank you @bredlix for the compa app!