So Google always keeping me in a manic state. I was able to update some faces for target SDK 33 using WFS 1.6.10 with no issues. The faces were updated and I was informed that “A recent policy violation in your app has been addressed”. Wonderful! I know what I am doing!..no I don’t!
I did the same thing with my next 3 apps putting the new WFS 1.6.10 on ALL tracks (internal, closed, open, production) and they have all passed into production but now the policy violation message is still there and I have not received the notices that the policy violation has been addressed which usually comes before the app gets passed review.
I first “upload” the new .aab in internal testing, then in closed, open and production I “add from library” adding the new .aab
I don’t understand how or why in so many cases in Google Play I think I get something right, have a smile on my face, and very quickly after I want to pull my hair out.
Please someone look at my process and tell me what you are doing that I am not?
current state of on face that was passed just today, but policy violation message is still there.
no companion app, only .aab from WFS created on Wear OS tracks in Google Play. My process did not change since the 4 faces that I got passed and cleared of policy violations but for these past 3 faces I have tried to update, the policy violation warning is still there - super frustrating!
Google requires the target SDK to be 34, not 33.
WFS only carries SDK 33, so you can’t get away with violating the policy.
Wait for WFS 1.7.0, but I think it will take a long time. Because new Android SDKs are usually not backward compatible with old SDKs, so they have a lot of things to update :))
I have already had 4 apps clear the SDK policy violation using WFS 1.6.10.?? That’s what the quick update to WFS 1.6.10 was for to begin with so people using WFS could update to the new policy requirements.???
here an example of a fixed policy issue from Google on my other apps.
@Swatchub.com, this is not correct. We could update to API 34 if WFS allows it in the next release, but In July, Google told all of us we would have to update our watch faces to target API 33 by the end of August (a few days away now) or we would no longer be able to update our faces. This means that we’ll be in compliance for at least one more year (until next August) as long as we are targeting API 33.
I’m reasonably sure this is also incorrect since the Android SDKs are built to be backwards compatible. This is normally achieved with the usage of “minSdkVersion” in the Android Manfest file to indicate how far back you want your app to be compatible. At work we have an app that is written for modern Android but compatible all the way back to Android 7. I’m not sure where you found information saying the SDKs are not backward compatible…
My point is I have gotten 4 apps updated to this level but my next 3 although passed and showing the new API/SDK in release overview but ARE NOT clearing the policy violation because I didn’t get the email saying that did so.
My question is to the WFS users out there that have managed to update to the new API/SDK as per the new policy requirements…what am I doing wrong?
From what you’ve shown here it looks like you’ve done what they asked. Does the policy violation message you are seeing specifically state the issue is with the target SDK for those faces? I am wondering if it could be some other policy violation since you appear to have resolved the SDK issue.
I have done nothing different with the 4 apps that got passed and resolved the policy issue.
So…I guess I’ll just make another .aab in WFS 1.6.10, up the version number/code by 1, put it on every track, submit it for review and wait another 3 or 4 days, close my eyes and throw darts at the wall until they stick.
