azavea / cac-tripplanner-android

GoPhillyGo Android app
https://gophillygo.org
Apache License 2.0
3 stars 3 forks source link

Test release via App Bundle, then generate and apply new upload key #205

Closed ktohalloran closed 1 year ago

ktohalloran commented 1 year ago

EDIT: Research as a part of issue #204 revealed that APKs are signed locally via both signing and upload keys and app bundles are signed locally via upload keys. We've mostly released via APKs but have released at least one app bundle, meaning that have used both upload and signing keys. Since we want to use Google App Signing, we need to release via app bundle (not APK) and therefore need to generate a new upload key to replace the old one. In order to isolate as many unknowns as possible, we should release an App Bundle with the old key, then use that process to release with the new key once it has been reset. This task is to complete the first half of this double release, including the resetting the upload key.

First, release the app with the old key via App Bundle by following and updating the Release instructions up through "Releasing to Google Play for Testing", adjusting for the shift to releasing via app bundle instead of APK.

Then, to replace the upload key, we should:

If we have time, we should: This should be spun out as its own issue if we don't end up having time in this card.