I received the email from Google you all probably received, and I have to update a ton of watch faces. Now, long story short, I have a doubt: Google wrote to remove any old aab from any release channel, but if I do so, users with an older smartwatch would stop seeing my watch faces in the store. If I don’t remove them, instead, I’m afraid that Google could enforce some kind of action. What do you think?
How are we to remove them anyway? Don’t we just have to make a new .aab in 1.8.7 + and then upload/overwrite it on to any tracks that an old .aab may be on in an app?
Also, speaking of doubts, the wording regarding monetization seems open to interpretation here. I hope this is referring to any watch faces that are not updated to 1.8.7+ after January 14, 2026.
Right??
Crickets again…
“What’s the first rule about Google Play Console questions?”
“We do not talk about or share any information about Google Play Console.”
@MergeLabs I think they are talking about legacy watch faces when mentioning monetization. Since both of the points above are talking about legacy watch faces as well.
I certainly hope so. The fact that you also said “I think” shows maybe you have a little doubt too? 
All Google had to do was include something like…
Monetization: New one-off watch face purchases, in-app purchases, and subscriptions will no longer be possible ‘for watch faces/apps that have not been updated to 1.8.7+’, but existing purchases and subscriptions will continue to work.
I am sure it’s just fine but it freaked me out for a moment I am not gonna lie.
Now, off to figure out just exactly Google wants me to do before January 14, 2026.
1 Like