You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Sign with an upload certificate (stored on our CI server)
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: