I just would like to express my frustration in releasing apps in GooglePlayConsole. To date out of 15 apps, 9 has been rejected, unpublished and opted-out of Wear OS.
I’m sure that there is something wrong with the way I build it on WFS. The irony is that even if I recycle a successfully published app with new package ID, with cosmetic changes, it still gets rejected.
Received same rejection yesterday. It looks like some lazy tester wasnt able to push watch face into watch so he gave that unfortunate reason. I had no problem for like 6 weeks. Anyway. Just resubmit .aab with higher version number & also fill complain (policy status - rejection reason) & pick app does not install & action taken against your app was too harsh. It should get approved quickly in case they will not find any other stupid reason like tiny grey border around watch face screenshot (which isnt visible on watch)
Complete waste of time those feedbacks on rejection I think ive had 2 success out of many complaints to the reasons they give to it failing. Its quicker just to publish a new release I found which takes a day or so.
One of the issues was the inclusion of watches that did not have on body sensors and that was fixed in the WFS 1.0.12 release
But I think there is other issues that need to be worked out.
It uses internal heart services component, listens for WHS change, writes data to temporary datastore & provides value within custom complication. If you set S Health to measure continuously, it should update complication every time there’s an update from WHS. Remember that continuous HR measurement is huge battery drainer. I’m using it with 10min interval set in S Health. Be sure to re-launch app after watch restart.