ScreenTinker 22376710ee fix(android): re-sign release APK with v1 (JAR) signature for MDM signage (#81) ... 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>		2026-06-11 21:10:04 -05:00
..
src	feat(scheduling): per-item schedule blocks (#74 dayparting, #75 auto-expire)	2026-06-11 15:46:41 -05:00
build.gradle.kts	fix(android): re-sign release APK with v1 (JAR) signature for MDM signage (#81)	2026-06-11 21:10:04 -05:00
proguard-rules.pro	Initial open source release	2026-04-08 12:14:53 -05:00