diff options
Diffstat (limited to 'packages/meshbay-android/README.md')
| -rw-r--r-- | packages/meshbay-android/README.md | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/packages/meshbay-android/README.md b/packages/meshbay-android/README.md index adb7e66..02297c9 100644 --- a/packages/meshbay-android/README.md +++ b/packages/meshbay-android/README.md @@ -30,11 +30,17 @@ holds the same service and the same visibility, for as long as it plays ```bash # needs JDK 17+ and an Android SDK (ANDROID_HOME, or sdk.dir in local.properties) -./gradlew assembleDebug # app/build/outputs/apk/debug/app-debug.apk -./gradlew testDebugUnitTest # JVM unit tests -./gradlew assembleRelease # app/build/outputs/apk/release/app-release.apk +./gradlew assembleDebug # app/build/outputs/apk/{full,play}/debug/ +./gradlew testFullDebugUnitTest # JVM unit tests +./gradlew assembleRelease # app/build/outputs/apk/full/release/app-full-release.apk + # app/build/outputs/apk/play/release/app-play-release.apk ``` +Two builds of the same application, same id and key: `full` is the one +distributed directly; `play` is for the Play Store, whose policy gives +READ_SMS to the default SMS application only, so it has no text messages +backup (no permission, no code: `src/full`, `src/play`). + A release is signed with the release key, which never enters the repository. `assembleRelease` reads it from `~/.gradle/gradle.properties`, and stops if any of these is missing rather than signing with the debug key: @@ -46,7 +52,7 @@ meshbayReleaseKeyAlias=meshbay meshbayReleaseKeyPassword=... ``` -`apksigner verify --print-certs app-release.apk` prints the certificate's +`apksigner verify --print-certs app-full-release.apk` prints the certificate's SHA-256 fingerprint, the one the download page publishes (§8.2). A release does not install over a debug build, or the reverse: the keys differ. |