5 ms·

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 updatin

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.

jarm0 3y ago
Agreed about conflicting message. And even better - e-mail was pretty vague and had to Google a separate link (https://support.google.com/googleplay/android-developer/answer/11926878?hl=en https://support.google.com/googleplay/android-developer/answ...) for more info. If I could go back in time then I would press that button, which asks for time until November, because as happened to us - it was not possible to go back to previous version in any way.
- wouldbecouldbe 3y ago
  Yeah you just saved me; was working late last night to get all updated. But still some issues; and was worried about testing. So thank you. Sorry you didn't see it on timme
- wouldbecouldbe 3y ago
  Now that I've check all accounts of several clients. 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.
sirius87 3y ago
I shudder to think what happens in another 5 years or so when the min target is bumped. We have an app built with about 6-8 Jetpack Compose libraries that is already flaky (even after using BOM) and only a magic combination of library versions ensures the app runs across SDK versions. 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.
ElliotH 3y ago
If you target SDK < 31 then you’ll see reduced availability on the store. That means users with phones running Android higher than your maximum targeted version won’t be able to newly acquire it. Existing users are unaffected. 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/thread/231996197/target-api-level-extension-form-new-help-content?hl=en-GB&sjid=7814240696333911601-EU https://support.google.com/googleplay/android-developer/thre... helps clarify too.
- wouldbecouldbe 3y ago
  Ah, okay now I get it. However out of 30 clients, we also have one app receiving no warning at all.
  - wouldbecouldbe 3y ago
    Who is on 31

jarm0 3y ago

Agreed about conflicting message. And even better - e-mail was pretty vague and had to Google a separate link (https://support.google.com/googleplay/android-developer/answer/11926878?hl=en https://support.google.com/googleplay/android-developer/answ...) for more info. If I could go back in time then I would press that button, which asks for time until November, because as happened to us - it was not possible to go back to previous version in any way.

wouldbecouldbe 3y ago
Yeah you just saved me; was working late last night to get all updated. But still some issues; and was worried about testing. So thank you. Sorry you didn't see it on timme
wouldbecouldbe 3y ago
Now that I've check all accounts of several clients. 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.

sirius87 3y ago

I shudder to think what happens in another 5 years or so when the min target is bumped. We have an app built with about 6-8 Jetpack Compose libraries that is already flaky (even after using BOM) and only a magic combination of library versions ensures the app runs across SDK versions. 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.

ElliotH 3y ago

If you target SDK < 31 then you’ll see reduced availability on the store. That means users with phones running Android higher than your maximum targeted version won’t be able to newly acquire it. Existing users are unaffected. 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/thread/231996197/target-api-level-extension-form-new-help-content?hl=en-GB&sjid=7814240696333911601-EU https://support.google.com/googleplay/android-developer/thre... helps clarify too.

wouldbecouldbe 3y ago
Ah, okay now I get it. However out of 30 clients, we also have one app receiving no warning at all.
- wouldbecouldbe 3y ago
  Who is on 31