[PWA Builder]: Support for Android SDK 34

[kiajiko]

Tell us about your feature idea

Google again changed the API level requirements.
App must target Android 14 (API level 34) or higher starting from Aug 31, 2024

Current supported version is 33

bubblewrap does not seem to be updated so far, too.

Do you have an implementation or a solution in mind?

Download source code from pwabuilder.com and compile with new version.

Have you considered any alternatives?

No response

[jere-mie]

Why put a start date of Aug 31, 2024 if they're going to start enforcing it sooner 😭 hopefully this gets fixed soon enough. My guess is it isn't an issue on PWABuilder's side, rather on Bubblewrap's side

[Blurazzle]

Jeremie Bornais (@jere-mie) Yes, remarkable, I noticed that too. Maybe the different teams within Google are not aligned.
https://developer.android.com/google/play/requirements/target-sdk?authuser=2

[SheepBroadcast]

Same here

[userofit123]

Been having this for a few days also

[MrAntix]

Please use the thumbs up on the original issue, don't "same here" the thumbs up will bring attention better and leave the issue readable down the line - thank you :)

[Twey]

In the meantime you can work around this by changing the targetSdkVersion in the manifest manually. You'll need zip, protoc, bundletool, and a JDK (e.g. OpenJDK) for jarsigner.

• unzip https://maven.google.com/com/android/tools/build/aapt2-proto/3.6.3-6040484/aapt2-proto-3.6.3-6040484.jar to the directory $AAPT_PROTO
• unzip your PWABuilder-built AAB (unzip YourApp.aab) and cd base
• decode the manifest: protoc -I $AAPT_PROTO Resources.proto --decode=aapt.pb.XmlNode <manifest/AndroidManifest.xml >manifest.txt
• edit targetSdkVersion in the manifest.txt and change int_decimal_value: 33 to int_decimal_value: 34
• reencode the manifest: protoc -I $AAPT_PROTO Resources.proto --encode=aapt.pb.XmlNode >manifest/AndroidManifest.xml <manifest.txt
• zip up your base directory: zip -r base.zip *
• use bundletool to bundle up the base module: bundletool build-bundle --modules base.zip --output your-app-signed.aab
• use jarsigner to sign your new AAB: jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 -keystore signing.keystore your-app-signed.aab my-key-alias (enter the keystore password and key password from signing-key-info.txt when asked)
• submit your-app-signed.aab to the Play store

[maiconcarraro]

^ There is also another easy workaround if you can use Android Studio, you can select to include Source code while generating the Android package on PWABuilder, so you can open the project and update the compilesdk/targetsdk, and build/sign again.

[jgw96]

Hello all! Sorry for the delay, I was on holiday for July 4th here in the US. I am working with our team to get Bubblewrap + PWABuilder updated and will post here when things are updated. Both James Kay (@Twey) and Maicon Carraro (@maiconcarraro) 's workarounds are great. Using Android Studio is what I would recommend for now if you are blocked.

[jgw96]

And this is the issue to get Bubblewrap updated GoogleChromeLabs/bubblewrap#860

[Blurazzle]

Justin Willis (@jgw96) and Maicon Carraro (@maiconcarraro)

After changing the compile and target SDK in the build.gradle file, some warnings are shown when compiling the project.

[kiajiko]

@jonkerw85
I was able to update it using Android Studio Koala | 2024.1.1, then installed Gradle version 8.7 in studio, after that updated Gradle plugin to 8.5 version in studio, which supports SDK 34. Then installed SDK 34 in studio. Then changed target sdk, compile sdk to 34 version.
Compilation returned only two unimportant warnings. Easily fixed one of them (it was clear what to change, but unfortunately do not remember what was that about), the second one was related to some deprecated function in 9.0 version.
Then Generated signed aab/apk in studio without issues. New version of my app passed google validation and update is already available in Google Play Store.