Skip to content

fix: Use consistent signing keystore for Android CI builds#232

Merged
macterra merged 3 commits intomainfrom
231-android-signing-key
Mar 17, 2026
Merged

fix: Use consistent signing keystore for Android CI builds#232
macterra merged 3 commits intomainfrom
231-android-signing-key

Conversation

@macterra
Copy link
Collaborator

@macterra macterra commented Mar 17, 2026

Summary

  • Decode ANDROID_KEYSTORE_BASE64 secret in both Android build workflows and pass keystore path/credentials as env vars to Gradle
  • Add signingConfigs.ci block in build.gradle that activates only when ANDROID_KEYSTORE_FILE env var is set (falls back to default debug signing locally)
  • Add *.keystore to .gitignore

Closes #231

Test plan

  • Manual build on branch completes successfully
  • Install new APK over existing without uninstalling

🤖 Generated with Claude Code

macterra and others added 3 commits March 17, 2026 17:19
Store keystore as a GitHub secret (ANDROID_KEYSTORE_BASE64) and decode
it in both Android build workflows so all CI builds are signed with the
same key, allowing in-place APK updates without uninstalling.

Also add *.keystore to .gitignore.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@macterra macterra merged commit 535e4e2 into main Mar 17, 2026
14 checks passed
@macterra macterra deleted the 231-android-signing-key branch March 17, 2026 21:50
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.

Use consistent signing keystore for Android CI builds

1 participant