Watch face rejected app uses BODY_SENSORS permission

Even I had tried without in the full description too, it was also rejected. SS are belongs to my last update.

I believe the guy who control this, press to cancel whatever I publish :slight_smile:

You know, you are not wrong about that. I don’t know anything about the tester process or whether or not it’s completely run by AI now or not. For a while, I was getting my faces rejected with no specific reason other than “fails to launch or crashes”. It drove me absolutely crazy. When I appealed I kept getting responses from the same “guy”, but I dont know if they are real or not, and they said they cannot provide specifics and to refer to the policy guide. (basically F**K OFF). I finally just gave up and unpublished the watches (because a couple were passes but rejected when I updated). I then REMADE the watch faces again in a totally new WFS file and version. I was having all those problems in WFS 1.6.9 but after I got 1.6.10 I have had no issues and the watches that I remade passed with no issues either. It’s extremely frustrating and just a reminder that Google does not care about you at all. LOL

2 Likes

I use also 1.6.10

Maybe the dummy app makes the problem. I will try to new app without dummy first.

It is solved by ;

Creating a new app and uploaded it without dummy app first. When it is approved, I uploaded the dummy app and now it is also approved.
It means , it is not only about what you selected for health app policy.

FYI.