fix(ci): sign debug builds with a committed keystore so debug-latest updates in place - #155
Merged
Conversation
…updates in place The Publish-debug-APK workflow runs assembleDebug on a fresh runner, which auto-generates a throwaway ~/.android/debug.keystore per run — so every debug-latest build was signed with a different key and could not update an existing install (INSTALL_FAILED_UPDATE_INCOMPATIBLE → uninstall + data wipe), contradicting the release notes. Commit a fixed debug keystore (standard non-secret creds: android / androiddebugkey, backdated per the Android debug-key convention) and point the debug signingConfig at it, so every debug build — local and on every CI runner — shares one stable signature. `signingReport` confirms the debug variant now resolves apps/taskmind/debug.keystore with a stable fingerprint. .gitignore keeps *.keystore ignored and un-ignores only this one debug key; release signing is untouched. Closes #154
This was referenced Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #154. Second (and final) half of batch 1 — the CI-signing fix from the whole-repo review's #1 finding.
The bug
release-apk.ymlruns./gradlew :apps:taskmind:assembleDebugon a fresh GitHub runner, which auto-generates a throwaway~/.android/debug.keystoreper run. So everydebug-latestbuild is signed with a different key, and installing a newer one over an older one fails withINSTALL_FAILED_UPDATE_INCOMPATIBLE→ the user must uninstall, wiping all their data — the exact opposite of the release notes' "updates in place and keeps your data".The fix
Give every debug build one stable, reproducible signature:
apps/taskmind/debug.keystore— standard non-secret debug credentials (android/androiddebugkey), PKCS12, backdated per the Android debug-key convention (defends against device clock-skew). The default Android debug key is globally shared, so this is not a secret..gitignorekeeps*.keystoreignored but un-ignores only this one debug key (!apps/taskmind/debug.keystore). Real release keys /keystore.propertiesstay ignored.build.gradle.ktsoverrides the built-indebugsigningConfigto point at the committed keystore and assigns it tobuildTypes.debug.Verified
./gradlew :apps:taskmind:signingReport→ thedebug(anddebugAndroidTest) variants now resolveStore: apps/taskmind/debug.keystore, aliasandroiddebugkey, with a stable SHA1 — that stability is exactly what letsdebug-latestupdate in place.Scope / caveats
Adversarially reviewed across build-correctness / security-scope / CI-path dimensions: 0 confirmed findings.