Skip to content

Change to sign the APK with the actual keystore#3307

Open
hwangsihu wants to merge 1 commit into
masterfrom
debug-android-sign
Open

Change to sign the APK with the actual keystore#3307
hwangsihu wants to merge 1 commit into
masterfrom
debug-android-sign

Conversation

@hwangsihu

Copy link
Copy Markdown
Contributor

@bear101, could you please add the information about the keystore used for Google Play releases to your GitHub Secret? The required items are as follows:

  • ANDROID_KEYSTORE_BASE64 (You need to base64 encode your keystore)
  • ANDROID_KEYSTORE_PASSWORD
  • ANDROID_KEY_ALIAS
  • ANDROID_KEY_PASSWORD

@hwangsihu hwangsihu requested a review from a team as a code owner May 31, 2026 02:08
@bear101

bear101 commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

I tried adding the secrets but it didn't seem to work. Also how do I prevent file key.keystore from being stolen? Or people echo'ing ANDROID_KEY_PASSWORD

@hwangsihu

Copy link
Copy Markdown
Contributor Author

Since Secret is encrypted with ***, I don't think you need to worry about that.

@Nardol

Nardol commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

If I agree about echo, I won't really agree to say all is OK.
A member of the organisation which would make a bad PR could transform the key to send it somewhere else.
Adding the secret is only the beginning:
it should not be used in a PR, only in some precise scenarios, in a protected environment...
For example this kind of secret should be used in a workflow which should only be manually dispatched.
The GitHub documentation gives a lot of information and links.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants