Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate app signing keys #69

Open
Lineflyer opened this issue Mar 8, 2020 · 0 comments
Open

Migrate app signing keys #69

Lineflyer opened this issue Mar 8, 2020 · 0 comments
Labels
CI server / Build tools Issues with our CI server or other build/dev tools

Comments

@Lineflyer
Copy link
Member

As clarified in #52 we currently have to use a two step approach to sign the app for publishing on Google Play due to historic reasons:

  1. Sign with an upload certificate (stored on our CI server)
  2. Final signature with official app keys happens when uploading the APK to Google Play using this upload certificate

The downside of this approach is, that APK files produced by our CI server (such as nightlies and PR builds) can not be installed as upgrades of the official version.

While this is only a minor problem, it would however desirable to use the same keys everywhere.
As @menion mentioned in a comment we should revisit this topic once the existing keys need to be renewed anyway.
@Lineflyer Lineflyer added the CI server / Build tools Issues with our CI server or other build/dev tools label Mar 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CI server / Build tools Issues with our CI server or other build/dev tools
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Lineflyer