Android Google Play internal testing (TestFlight analog)

[erik-sutton95]

What problem does this solve?

iOS already ships to testers from main via Xcode Cloud → TestFlight. Android is operator-ready in-tree (just android-check, physical shell) but not on Google Play. Testers sideload debug APKs. ROADMAP Next is Play internal testing. Issue #70 (Android parity) explicitly left Play listing out of scope and is now done.

Proposed solution

Mirror OpenZCine’s Play Internal path, phone only (no Wear):

• Signed bundleRelease AAB from CI
• Upload to Play internal testing when Android/core paths land on main
• Same product version as iOS (openpocketcine.versionName = MARKETING_VERSION)
• CI-stamped versionCode (do not commit every build)
• Kill switch PLAY_UPLOAD_ENABLED
• Upload keystore + Play service account in a play GitHub environment — never git

First track is internal testing, not production/open testing.

Alternatives considered

• Fastlane supply only (still need signing + console)
• GitHub assembleDebug forever (not what testers install from Play)
• Production track on day one (no)

Area

Android app / Build / development

[erik-sutton95]

Maintainer task tree:

• Parent: Android Play internal pipeline (signed AAB from main) #140
• Signed AAB: Gradle: signed bundleRelease + local upload keystore #141
• Play Console (human): Play Console: create app, internal testers, first manual AAB #142
• CI upload: CI: play-internal.yml uploads signed AAB on main #143
• Docs: Docs: Android Play internal as the TestFlight analog #144