[INFRA]: Sign GitHub release APKs with a stable key
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 25/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Dart
- Estrellas
- 9
- Forks
- 5
- Merge medio
- 49 min
- PR fusionados (30 d)
- 34
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CommandLineCoding/Elephant
-
area: mobile chore good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
CommandLineCoding/Elephant#247 ·
Los mantenedores suelen responder en 1 día
-
area: mobile bug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
CommandLineCoding/Elephant#245 ·
Los mantenedores suelen responder en 1 día
-
area: mobile enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
CommandLineCoding/Elephant#183 ·
Los mantenedores suelen responder en 1 día
-
area: mobile difficulty: medium enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 56/100
CommandLineCoding/Elephant#249 ·
Los mantenedores suelen responder en 1 día
-
area: mobile chore difficulty: medium testing
Dificultad 4/5 3-5 días Aptitud para principiantes 66/100
CommandLineCoding/Elephant#248 ·
Los mantenedores suelen responder en 1 día
Todos los issues de CommandLineCoding/Elephant
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 76/100
livekit/client-sdk-flutter#1281 ·
Los mantenedores suelen responder en 4 días
-
android bug priority: P1 qa
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
GHRik/bielik_oneclick_launcher#55 ·
Los mantenedores suelen responder en 1 día
-
SchedulerBinding.requestPerformanceMode(mode) does not forward the requested mode to the engine.Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
carp demo apps enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
carp-dk/carp.sensing-flutter#670 ·
-
[BUG] IP 质量类型误判：ISP 静态段被显示为机房Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100