I submitted update on same date 23 Jul as you for just 1 watch face aab i updated with latest WFS 1.6.10. Unusual delays in app update approvals.
i made 0 changes to watchface . Only it was rebuilt in latest WFS .
I think changes are being implemented for Wear OS 5 by Google. Also its the same time of year when a new Google Pixel Watch is coming out.
I f you remember when Google Pixel 1st watch came out there were so many issues like app approvals and download button missing issues
Same here, I updated four of my apps on July 23rd. For two of them, I had only added further translations of the PlayStore entries and these were approved a few hours later. For the two where I actually used the new WatchFaceStudio version, the approval has been pending ever since
New version is here, I will try
I volunteer to be a tester, for the bright future of all of us. Donāt forget me if bots block me
I will update first 20-30 faces, both companion and wear.
(I hope that Samsung team will check with Play team what is the problem with account terminationā¦)
when uploading gives error some abb files : (upgrade for sdk33)
Android App Bundle is signed with the wrong key. Make sure your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with the following fingerprint
SHA1: AD:AE:62:A2:74:FC:1F:22:Fā¦
The certificate used to sign the App Bundle you installed has the following fingerprint:
SHA1: 08:AF:07:24:37:56:E6:2F:ā¦
how can i fix it ?
i changed key ailas code with the old one gived error again!
I sent some updates too and they were validatedā¦ My account is still there and it wasnāt terminated by the crazy accountā¦ Letās hope they arrested himā¦
The new version should remember to connect watch face studio to galaxy watch, only need to connect once. It will be very inconvenient to turn on the wireless connection continuously, after 1 hour the wireless connection will turn off automatically. This causes great difficulty when having to test many watch faces
I know it. So, If they offer a solution to maintain connections or allow quick connections, it will be much better than the current manual connection.
Currently, connecting devices only requires 1 touch, this is software designed for developers, but having to manually enter many parameters many times is too bad.
Quick update on my earlier message: iāve updated both my public/published faces and the ones in testing. all of the updates have been approved. i got the message for the ones in testing that they now comply with the 33 SDK policy. however, Iām yet to receive the same message for the published ones. will update once i do.
Hi, my app build with WFS 1.6.10 have already been reviewed with no issues butā¦
But I am bit worry coz the warning still remain thereā¦
No companion app in this watchface, only WFS file.
I made 0 changes to watchface, only rebuild it with WFS 1.6.10(increase ver number).
I create new Wear OS release, and submit.
Is my above step correct?
In the app bundles, the target SDK show change to 33, but the API levels still the same 30+.
Is your same, API level show 30+?
Just to double check is my above step correct?
If all is correct, should I just ignore the warning?
