I’m still working on the updates. Was quite a lot of libraries to update for us. And only got the warnings last weekend.
Anyone knows the impact of not updating on time? Google’s message seems conflicting.
Anyone knows the impact of not updating on time? Google’s message seems conflicting.
It's very mixed. Some haven't received a warning.
Some have a warning that no updates can be published.
Some have 2 warnings; one that no updates can be published & one that it won't be available to new users.
If you target SDK < 33 then you need to update to SDK 33 because you won’t be able to make releases with the old target SDK anymore. (Existing bundles are fine). If you miss the deadline it doesn’t introduce further enforcement than that but it might mean if you had an urgent update you’d need to update the target SDK at that time. So sooner is better.
Both have extensions available to Nov 1.
Wear has different thresholds.
Hopefully https://support.google.com/googleplay/android-developer/thre... helps clarify too.
However out of 30 clients, we also have one app receiving no warning at all.
If you think developer libraries provided by Google for Android are stable, battle-tested and you feel this is akin to first-party "platform code", please be advised that it can be a hellscape with you fighting Google's build tools and the IDE/dev env on one side and zero help on SO to debug device-specific issues with lengthy stacktraces on the other. You end up landing on an Android issue-tracker where some kind soul mentioned the device name, only to find that issue in limbo asking for a working reproduction.