Use Android build tools for APK validation

This commit is contained in:
2026-07-28 23:50:37 +02:00
parent 16e9eebc3d
commit ae4a95a337
4 changed files with 82 additions and 40 deletions

View File

@@ -6,7 +6,7 @@ Install free Android apps via ADB from F-Droid, GitHub Releases, or GitLab Relea
- Python 3.11+
- `adb` (Android Debug Bridge) in PATH
- `apkanalyzer` (Android SDK tools) in PATH
- `aapt2` or `aapt` (Android SDK Build Tools) in PATH
## Quick start
@@ -43,8 +43,10 @@ Every application also requires `name` and `package`. For GitHub and GitLab,
set `asset_pattern` when a release contains more than one suitable APK. Debug,
test and unsigned APKs are rejected by default.
`apkanalyzer` is mandatory and must be available in `PATH`. It is provided by
the Android SDK command-line tools.
`aapt2` is used to validate the APK package ID before installation, with
`aapt` as a fallback for older Android SDK Build Tools. At least one of them
must be available in `PATH`. The script refuses to install an APK when neither
tool can validate it.
For Wi-Fi ADB, configure an explicit address after enabling wireless debugging: