Bump targetSdkVersion to 36

[A1kmm]

Everything tests okay with a simple PWA after upgrading, and passes Google Play's Quick Checks.

35 is going to be unsupported for publishing new versions to Google Play from the end of August according to https://support.google.com/googleplay/android-developer/answer/11926878.

[Ubeydu]

I was working on the same bump when this PR appeared: I had claimed it in #1047 earlier today, and I opened #1051 with my version shortly after this one. Rather than compete, I want to add my test results here, because they verify the exact template change this PR makes.

My branch carries the identical targetSdkVersion 36 line, plus a BUILD_TOOLS_VERSION bump. With that branch:

• npm build, lint and test are green on all three packages.
• I generated the TWA for my production PWA (com.akluma.app, currently in closed testing on Google Play) with the patched CLI, and the generated project gets targetSdkVersion 36.
• aapt2 badging on the built APK reports targetSdkVersion 36, and the signature verifies against the app's existing upload key.
• The app installs and runs on an Android 16 (API 36) emulator: full-screen launch, with Digital Asset Links verification working.

One question for the maintainers: #764 and #862 both paired the target bump with a BUILD_TOOLS_VERSION bump (39d5972). Leaving it at 34.0.0 works, since it only drives the sdkmanager install and the zipalign/apksigner paths, but if the pairing is worth keeping, that companion change is in #1051.

[JudahGabriel]

@gstepniewski-google Can we get a review on this? It's rather time-sensitive with the new Google Play requirements.

[leeobrum]

I am eagerly awaiting this PA

[gstepniewski-google]

Merged #1051

[JudahGabriel]

Thanks Greg!

[ghnp5]

Hi @gstepniewski-google

Do you confirm that this change is really included in the last release?

When I use the latest Docker container (ghcr.io/googlechromelabs/bubblewrap:latest, after pulling it),
and then run bubblewrap init,

the result is still targetSdkVersion 35 in build.gradle.

I know I can update it manually, but I was expecting bubblewrap to do it for me.

Thanks!

[ghnp5]

Maybe this is the reason: pwa-builder/PWABuilder#6159 (comment)

But that means that whenever the NPM version is released, the docker image needs to be updated too, so it can pull the latest npm package.

[JudahGabriel]

@ghnp5 No, these are separate issues. PWABuilder doesn't rely on the Docker container for Bubblewrap. We have our own container.