This repository has been archived by the owner on May 28, 2024. It is now read-only.
Make Android debug releases a flavour #50
Labels
part:infrastructure
Affects anything that is not user facing (building, testing, deployment, legal, marketing)
platform:android-only
This only affects Android platform
type:improvement
Makes the software better or more usable
Milestone
Comments
llucax
added
type:improvement
llucax
added a commit
that referenced
this issue
Mar 12, 2021
If we use the --release flag, then the app needs the release signing key, but we don't want to do that for now. For more details see: #50 Signed-off-by: Leandro Lucarella <[email protected]>
llucax
added a commit
that referenced
this issue
Mar 12, 2021
If we use the --release flag, then the app needs the release signing key, but we don't want to do that for now. For more details see: #50 Signed-off-by: Leandro Lucarella <[email protected]>
|
On signing keys action (we probably want to do our own for security reasons, but as an example): https://github.com/r0adkll/sign-android-release. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ideally an Android app with a particular ID should be associated to one particular signing key.
When building Android APKs/App bundles in the CI, we should sign them if they are compiled with
--release(right now they are not, as of #49). But if we do so, we need to either use the production signing key (probably bad) or use a different signing key, but then the app won't be upgradable if downloaded from the artifacts as the keys don't match.Probably the best solution is to create a new Android ID (like
me.noclick.app.debug) and have a special signing key for that, which can be used to sign automatically for release artifacts produced by the CI.The text was updated successfully, but these errors were encountered: