Use newer signature scheme in E2E tests - Githubissues

bitrise-steplib / steps-google-play-deploy

MIT License

54 stars 35 forks source link

Use newer signature scheme in E2E tests #139

Closed ofalvai closed 2 years ago

ofalvai commented 2 years ago

Checklist

[X] I've read and followed the Contribution Guidelines
[X] step.yml and README.md is updated with the changes (if needed)

Version

Requires NO version update

Context

E2E tests are failing because our tests apps' targetSdkVersion is 29, but the minimum required version is 30 starting from November.

Updated the version in the sample app in https://github.com/bitrise-io/sample-apps-android-sdk22/pull/18, but the new targetSdkVersion also means that Google Play rejects apps signed with signature scheme v1.

Changes

Use apksigner in the signing step so that the apps are signed with a newer signature scheme (v4 probably based on minSdkVersion of the app)

Investigation details

Decisions