"An SDK version you are using has been reported as outdated" warning in Google Play Console

Question

"An SDK version you are using has been reported as outdated" warning in Google Play Console

david-buck opened this issue a year ago · 25 comments

david-buck commented a year ago

I am getting this message in Google Play Console for two out of three of my apps created using Bubblewrap.

The SDK developer androidx.fragment has reported fragment:1.0.0 as outdated. Consider upgrading to a newer version.

Is there something I can do, or is it a case of waiting for an update to Bubblewrap/Android Browser Helper?

Thanks,

david-buck commented a year ago

Yes I did

Answer 1 · 2023-07-13T07:40:03.000Z

Yep I am getting the same. I assume Bubblewrap needs to update the SDK they are using.

Answer 2 · 2023-07-13T09:23:21.000Z

Hum, Bubblewrap doesn't include this library directly, so I'm guessing it's a transitive dependency from https://github.com/GoogleChrome/android-browser-helper/. Are you using the location delegation or play billing features?

Answer 3 · 2023-07-13T09:38:17.000Z

It seems the Play Service location library includes Play Services Base, which in turn includes AndroidX Fragments. So, the solution is to bump the version on android-browser-helper so it can also be bumped in Bubblewrap.

Answer 4 · 2023-07-13T11:54:36.000Z

Are you using the location delegation or play billing features?

Yes, the apps getting this warning use location delegation, the one not getting this warning does not.

Thanks

Answer 5 · 2023-07-17T12:21:20.000Z

I'm getting this and I have no clue what location delegation even is.

Answer 6 · 2023-07-17T12:35:53.000Z

@GCSBOSS Check your twa-manifest.json and the features section. If your web application doesn't use the Location API, you can probably disable it (and make your APK slightly smaller)

Answer 7 · 2023-08-01T15:42:04.000Z

android-browser-helper has been updated to use a newer version of play-services-location: GoogleChrome/android-browser-helper#437. One a new version of the library is published we can update Bubblewrap.

Answer 8 · 2023-08-07T11:46:18.000Z

Deployed on Bubblewrap 1.21.0

Answer 9 · 2023-08-07T23:38:11.000Z

This may be a stilly question, so please forgive me but, how does this not require a version bump in ABH?

Answer 10 · 2023-08-08T09:16:27.000Z

The library causing the warning is included via the locationdelegation part of ABH, which was updated via #819. There's no need to update the core library

Answer 11 · 2023-08-08T10:59:49.000Z

I have reinstalled @bubblewrap/cli to get the latest version and am still getting this error in Play Store Connect:

bubblewrap --version is returning version 1.21.0

Do I need to reenable alphaDependencies or something?

Answer 12 · 2023-08-08T11:52:12.000Z

Did you run bubblewrap update after updating to the last version and before rebuilding the APK?

Answer 13 · 2023-08-20T11:20:25.000Z

I am getting this error too and I have very little knowledge of how all these codes work. I had somehow managed to get bubblewrap setup for my app.

Hope one of you would be able to guide what exactly I need to do in my app to get this problem fixed.

Answer 14 · 2023-08-21T01:29:41.000Z

@david-buck did your issue get resolved? This thread seems to be in "closed" status. I wonder if anyone will look at it now.

Answer 15 · 2023-08-21T02:44:15.000Z

@mghatiya no it didn't. I'm not sure what the next move is tbh. I opened the project in Android Studio and the correct dependency versions are showing in the gradle file, so I can't be sure if it's not just a classic Play Store issue.

Answer 16 · 2023-08-21T08:40:11.000Z

There may be another library being pulled in that Play is alerting about.

Answer 17 · 2023-08-21T10:02:29.000Z

This is the specific warning in Play

I did an update and build to generate the version for this screenshot.

Answer 18 · 2023-10-30T18:12:35.000Z

Hey @david-buck, did you manage to get this resolved? I am also on version 1.21.0 with the same warning popping up in Play console.

Answer 19 · 2023-11-02T11:03:58.000Z

No, I gave up. There's no obvious reason why bubblewrap is building with the wrong version.

Answer 20 · 2023-11-03T15:05:29.000Z

How do we bring people's attention to it? @david-buck maybe you can reopen the thread?

Answer 21 · 2024-02-12T12:40:40.000Z

I found some time to dig into this a bit more and I can't work out how the fix mentioned above was meant to solve it.

I cleared all gradle caches on my computer, cleared NPM caches, installed the latest JDK update, and reinstalled bubblewrap before looking into this.

By running a gradlew app:dependencies on the output of my bubblewrap build I see that theandroidx.fragment:fragment:1.0.0 dependency is being used by:

com.google.android.gms:play-services-base:18.1.0 which is a transitive dependency brought in by com.google.android.gms:play-services-location:21.0.1. and
com.google.android.gms:play-services-basement:18.1.0 which is also a transitive dependency of com.google.android.gms:play-services-location:21.0.1. which was the change in ABH made here

So my projects are using the right versions of play-services-base from ABH, but the dependencies are still not good.

My only hope is that the newer version of play-services-base (18.3.0) or com.google.android.gms:play-services-location (21.1.0) fixes this.

Please, @andreban , could you revisit this?

Answer 22 · 2024-02-16T03:17:17.000Z

In answer to this, it looks like Google's official packages are reliant on the outdated version https://mvnrepository.com/artifact/com.google.android.gms/play-services-base/18.3.0

I think we just have to ignore it until the deprecated version is updated in every upstream dependency.

Answer 23 · 2024-08-03T11:05:05.000Z

Can you just add an explicit dependency on the updated version?