mirror of
https://github.com/screentinker/screentinker.git
synced 2026-06-18 20:22:42 -06:00
minSdk 26 makes AGP default the v1 (JAR) signature off, so the release APK is v2-only. Some MDM-managed commercial signage (MAXHUB via the Pivot MDM) silently removes a v2-only app on the next reboot because its boot integrity check expects a v1 signature — screens that power-cycle nightly lose the app and fall back to the setup screen. `enableV1Signing = true` has no effect at minSdk >= 24 (verified: still v2-only). Instead, finalize assembleRelease with a `resignReleaseV1` task that re-signs via apksigner with --v1-signing-enabled true and a low --min-sdk-version, emitting v1 alongside v2/v3. Verified: v1+v2+v3 at min-sdk 19, verifies at API 36, and the re-signed APK installs and runs on a live API 36 emulator. Closes #81 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| app | ||
| gradle/wrapper | ||
| build.gradle.kts | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| settings.gradle.kts | ||