Repository navigation
Phone app: the dev client on Google Play's internal track (deploy#22) - #324
Merged
Merged
Conversation
…s one as OpenClapper Dev Local (deploy#22) Build phone app with variant dev and the environment's key builds "OpenClapper Dev" (org.openclapper.dev) as a signed release build with the build-time version code, APK and App Bundle, and takes track internal. The dev launcher and menu stay in that release build (expo.devlauncher/devmenu.configureInRelease). Without a key it stays the debug build, now "OpenClapper Dev Local" (org.openclapper.dev.local), as make dev-build is, so the two install side by side. STAGING_VERSION_CODE becomes BUILD_TIME_VERSION_CODE. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of OpenClapper-dev/deploy#22. The deploy side (a "Development · Build phone app" workflow) follows in that repository once this is on
main.What changed
build-phone-app.yml:variant: devtakestrack: internal. With the environment's four key secrets it builds a signed release:assembleRelease bundleRelease,APP_VARIANT=development, and the build-time version code. The debug-key check, the Play requirements step and the upload then run as they do for staging. Without a key it stays the debug build, as before. A track without a key fails in Settings.app.config.ts:development("OpenClapper Dev",org.openclapper.dev) is the Play dev client. It gets the build-time version code andwithDevClientInRelease. That plugin setsexpo.devlauncher.configureInReleaseandexpo.devmenu.configureInRelease; without them both modules compile themselves out of release builds (theirandroid/build.gradle).development-local("OpenClapper Dev Local",org.openclapper.dev.local) for keyless builds. It has the same scheme and icons, so Metro's QR code opens either app.STAGING_VERSION_CODEis renamed toBUILD_TIME_VERSION_CODE, because it is shared now.make dev-buildbuildsdevelopment-local.make mobilekeepsAPP_VARIANT=development, since only the scheme matters there.Decisions
org.openclapper.devinstead of replacing it. Uninstall the old one once.Checked
make checkis green.expo config --type introspectgivesdevelopment→org.openclapper.dev, the build-time code and both Gradle properties.development-local→org.openclapper.dev.local, the release code, no properties.bash -n. I simulated Settings for dev without a key (passes), dev + internal without a key (fails with the message), and dev + internal with a key (passes).Not checked
🤖 Generated with Claude Code