[INFRA]: Sign GitHub release APKs with a stable key
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 25/100
研究方向
Read .github/workflows/android-release.yaml at the “Set up release signing” step and mobile/android/app/build.gradle.kts at signingConfigs. The issue says this requires maintainer access to repository secrets, so a first-time contributor cannot complete the setup independently. Done means the release uses the stable keystore without the debug-key warning and the release notes explain the one-time reinstall.
由索引模型根據 Issue 內容生成。
描述
Context
The release workflow signs APKs with four secrets: ANDROID_KEYSTORE_BASE64, ANDROID_KEYSTORE_PASSWORD, ANDROID_KEY_ALIAS and ANDROID_KEY_PASSWORD. None of them is set on this repository, so every GitHub release so far was signed with a throwaway debug key. The v0.3.2 run logged:
ANDROID_KEYSTORE_BASE64 is not set; APKs are signed with a throwaway debug key and can't update each other.
Anyone who installs from GitHub Releases can't update to the next release in place: Android rejects it (INSTALL_FAILED_UPDATE_INCOMPATIBLE) and they have to uninstall, which deletes their local messages and keys. F-Droid builds are not affected (F-Droid signs them itself).
What to do
- Create a release keystore and keep a backup somewhere safe (losing it means the same problem again).
- Add the four repository secrets (
ANDROID_KEYSTORE_BASE64is the keystore file, base64-encoded). - Check that the next release run has no "throwaway debug key" warning.
- Say in the release notes that people who installed an earlier GitHub APK need to reinstall once.
Where to look
.github/workflows/android-release.yaml (step "Set up release signing"), mobile/android/app/build.gradle.kts (signingConfigs).
Good to know
Only a maintainer can do this, since it needs repository secrets. Ideally before tagging v0.3.3.
- 主要語言
- Dart
- 星號
- 9
- 分支
- 5
- 平均合併
- 49 分鐘
- 30 天內合併 PR
- 34
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
CommandLineCoding/Elephant 的其他 Issue
-
area: mobile chore good first issue
難度 2/5 1-3 小時 新手友好度 76/100
CommandLineCoding/Elephant#247 ·
維護者通常 1 天內回覆
-
area: mobile bug good first issue
難度 2/5 1-3 小時 新手友好度 88/100
CommandLineCoding/Elephant#245 ·
維護者通常 1 天內回覆
-
area: mobile enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100
CommandLineCoding/Elephant#183 ·
維護者通常 1 天內回覆
-
area: mobile difficulty: medium enhancement
難度 4/5 3-5 天 新手友好度 56/100
CommandLineCoding/Elephant#249 ·
維護者通常 1 天內回覆
-
area: mobile chore difficulty: medium testing
難度 4/5 3-5 天 新手友好度 66/100
CommandLineCoding/Elephant#248 ·
維護者通常 1 天內回覆
查看 CommandLineCoding/Elephant 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 76/100
livekit/client-sdk-flutter#1281 ·
維護者通常 4 天內回覆
-
android bug priority: P1 qa
難度 2/5 1-3 小時 新手友好度 72/100
GHRik/bielik_oneclick_launcher#55 ·
維護者通常 1 天內回覆
-
SchedulerBinding.requestPerformanceMode(mode) does not forward the requested mode to the engine.未關閉
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
carp demo apps enhancement
難度 2/5 1-3 小時 新手友好度 78/100
carp-dk/carp.sensing-flutter#670 ·
-
難度 2/5 1-3 小時 新手友好度 78/100