docs: caminho canônico do keystore de release Android - #463
Merged
Conversation
O keystore vive fora de qualquer worktree (~/.local/share/neko-finance/) porque worktrees de build são descartáveis; o keystore.properties é copiado para dentro do worktree com storeFile absoluto, nunca gerado ali. Registra também a armadilha do PKCS12 (keytool moderno ignora -keypass diferente de -storepass) e a instrução de backup do .jks + properties num cofre pessoal.
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.
O quê e por quê
O keystore de release Android precisa viver fora de qualquer worktree — worktrees de build são
descartáveis (
git worktree add ... --detach), então gerar o.jksdentro de um deles arriscaperdê-lo junto com a limpeza do worktree, como já aconteceu uma vez.
Este PR só documenta o fluxo já em uso: keystore em
~/.local/share/neko-finance/(fora do repo,durável),
keystore.propertiesao lado comstoreFileabsoluto, copiado (não gerado) parasrc-tauri/gen/android/keystore.propertiesem cada worktree de build. Também registra umaarmadilha real do
keytoolmoderno: o formato PKCS12 padrão não suporta senha de chave diferenteda senha de armazenamento — passar
-keypassdiferente é silenciosamente ignorado.Como verificar
docs/building-android.md, seção "1. Provisioning the release keystore" — único arquivo tocado.git diff origin/main..HEAD --statmostra apenas esse arquivo.