Hello … Here is a screenshot of a watchface that is currently being checked. API level is 30+ and Target SDK is 33 … just like you, but the warning message is gone.
And here is a screenshot of an approved update with WFS 1.6.10 with the notification of Google about the removal of the violation
Thanks…did the email saying that you have fixed the policy violation come at the same time your app was passed into production? Or did it come after/separately ?
The mail came about a day after I had submitted the update
ok…I’ll just wait and see what happens. Thanks.
121 views about a topic that seems relevant for the time and no one else has an experience to share about it? It’s just all smooth sailing here for everyone else? 
I notice that on your release review, it say “30 or higher” for APK level, whereas mine says “30+”?
That’s the only difference I can see.
Hello … I think that is because my console side is in German and I had it translated.
I hope so, it seems exactly the same and although it’s been 3 days since my app was passed, I expect the email saying I no longer violate the new policies soon.
Cheers man! Thanks for commenting and being helpful.
Hi, I have the same issue as ur. Still getting the policy violation warning after passed the review.
I waiting for a week, nothing change.
Yesterday, I resubmit the updated app to the internal testing track.
B4 that I only submit for production track.
Problem solved.
Thanks for your reply, I appreciate that.
Yeah I re-submitted and put new .aab on ALL tracks. Very quickly after, I got the message that the policy violation has been addressed yet the watch face is still in review.
For the longest time I have only been making an internal test track and then going straight to production track with no issues (until recently). I guess from now on I should put the .aab on all test tracks?
Hey … I never create an internal test or closed test.
Hehe looks like we all do things differently. Wouldn’t it be nice if we could all talk about the things we do in Google Play Console and help each other along? It seems like most here aren’t on board with that idea at all. 
Again, thank you for the help.
I will say though that I am having another problem with my apps in review getting rejected with the reason being that “the app fails to launch or crashed on installation”. Sometimes I get this, and sometimes I don’t for the last few releases or updates I have done. So far, the only way I can fix this is by changing something of no consequence in the app and crossing my fingers hoping it will pass, which they have passed so far. Of course, Google is no help so I have been racking my brain trying to figure out why this is happening. Maybe it is because I only did an internal test track and then went straight to production? Maybe the tester has no open/closed test app to work from so they just reject it out of hand?
@MergeLabs, some of the differences may be due to what account type each of us has chosen. I may be wrong about this, but I believe according to what I was reading in Google’s documentation, only “organization” type accounts are allowed to skip the testing tracks because it’s assumed you would most likely be doing your own testing internally at your company. I think “personal” accounts are required to start with testing before being allowed to move into release. But, I am very new to all of this, so I may have misinterpreted those details.
Some of my watch faces have the same issue. Even though new versions are installed and activated, I still see that the old version is active when I check this page. This is why the warning appears. I think this is an error originating from Google.
Yes I am also pretty sure that is new personal accounts that have to find 20 testers and have them test for 2 weeks before an app can go into production. That is my understanding anyway. Thankfully, I got my account before that new policy was implemented. I think around late 2023 and after have to go through this process. I am assuming that putting the .aab on all tracks would guarantee you have all your bases covered and that doing so wouldn’t be a bad thing? But who knows…
I have a private account and have developed since the GW4 WatchFaces for the Playstore and I have never carried out internal or closed test. There were never problems from Google.
Yo, how u manage to skip it?
For me, it is force to create internal testing during Advanced setting → Add Form factor
Before I can opt-in, I need to create internal testing.
You can opt-in wear os without create new release for internal testing?
I have no idea why it is different for me. How long have you had your account? Maybe it is due to any new guidelines for newer devs.
I can go directly to the release when creating the WF in the dashboard. It has always been like this
I just submitted a new update. In the screenshot you can see that I don’t have to take an internal and closed test.
yeah and I have always only done internal test then wait for it to become “internal testing”, then I immediately do a production track only. I have not had many problems at all until recently and I don’t even know if my problems are related to how I upload files to Google Play Console. It is interesting how wvwryone is doing things a little differently though.
