Skip to content

Development · Build phone app: the dev client to Google Play's internal track (#22) - #23

Merged
bubulux merged 1 commit into
mainfrom
feat/22-dev-client-play
Nov 12, 2026
Merged

bubulux merged 1 commit into
mainfrom
feat/22-dev-client-play

Conversation

@bubulux

@bubulux bubulux commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

Closes #22. Needs OpenClapper-dev/core#324 merged first: this workflow calls core's Build phone app @main, which only takes variant: dev with a track after that PR.

What changed

  • New workflow Development · Build phone app (ref, track). It runs core's reusable workflow with variant: dev and environment: development. With that environment's key it builds the signed "OpenClapper Dev" (org.openclapper.dev), APK + App Bundle, with a build-time version code. track: internal uploads the bundle.
  • README: the workflow table, a "Development client" section, and the development environment under Settings.
  • docs/instance.md: a history entry, and development added to the environments.

Decisions

  • The dev client has its own upload key and its own service account (play-uploader-development, invited on the dev app only), the same pattern as production and staging.
  • make dev-build stays, as "OpenClapper Dev Local" (org.openclapper.dev.local, core#324), next to the Play app.
  • Manual trigger only.

Setup before the first run (owner)

  1. bash core/scripts/keystore.sh ~/openclapper-android-key-dev OpenClapper-dev/deploy. Back up both files in Bitwarden. Put the four ANDROID_KEY* secrets in a new environment development (main only).
  2. Google Cloud project openclapper: create the service account play-uploader-development and a JSON key. Store the key as PLAY_SERVICE_ACCOUNT_JSON in development.
  3. Run Development · Build phone app with track: none and download the .aab.
  4. Play Console: Create app org.openclapper.dev → Internal testing → Create release, keep the Google-generated key, upload that .aab. Add yourself as a tester and open the opt-in link on the phone.
  5. Play Console → Users and permissions: invite play-uploader-development on the dev app only, with "Release apps to testing tracks".
  6. From then on, run it with track: internal.

Not checked

  • The workflow has not run yet. The core side is checked with make check, a config introspection and a simulated Settings step (see core#324).
  • The release-mode dev client has not been tried on a phone.

🤖 Generated with Claude Code

…al track (#22)

Core's Build phone app with variant dev and the development environment, on core's main or a ref. With
that environment's key it builds the signed "OpenClapper Dev" (org.openclapper.dev), and track internal
uploads its bundle. Needs core#324.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bubulux
bubulux merged commit 5a9141f into main Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dev client on Google Play: an internal track for OpenClapper Dev

1 participant