fix(ci): purge stale generated sources before publish build
publish-play-store.yml caches android/build + intermediates with a restore-keys prefix fallback. After the package rename, that fallback restored a generated autolinking tree (ReactNativeApplicationEntryPoint.java) referencing the OLD package ai.opencode.mobile.BuildConfig, so compileReleaseJavaWithJavac failed. Delete generated + intermediates before prebuild so they regenerate for cc.agentlabs.opencode. Build.yml has no Gradle cache, which is why it built the new package fine. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
9
.github/workflows/publish-play-store.yml
vendored
9
.github/workflows/publish-play-store.yml
vendored
@@ -63,6 +63,15 @@ jobs:
|
||||
node -e "const f='app.json';const j=require('./'+f);j.expo.android=j.expo.android||{};j.expo.android.versionCode=${{ github.run_number }};require('fs').writeFileSync(f,JSON.stringify(j,null,2)+'\n')"
|
||||
echo "versionCode now: $(node -p "require('./app.json').expo.android.versionCode")"
|
||||
|
||||
- name: Purge stale generated sources
|
||||
# The Android build cache (restore-keys prefix fallback) can restore a
|
||||
# generated autolinking tree from a previous package id. Gradle then
|
||||
# reuses ReactNativeApplicationEntryPoint.java referencing the OLD
|
||||
# package (ai.opencode.mobile.BuildConfig) and compileReleaseJavaWithJavac
|
||||
# fails. Delete generated sources so prebuild + Gradle regenerate them
|
||||
# for the current package (cc.agentlabs.opencode).
|
||||
run: rm -rf android/app/build/generated android/build/generated android/app/build/intermediates
|
||||
|
||||
- name: Expo prebuild
|
||||
run: npx expo prebuild --platform android --no-install
|
||||
|
||||
|
||||
@@ -201,7 +201,7 @@ For pushes/gh CLI on this repo: `source ~/.env.d/github-dzianisv.env`
|
||||
## Google Play Console
|
||||
|
||||
- **Developer account**: VIBE TECHNOLOGIES, LLC (ID: `8842655543970815326`), Google login `vibeteaichnologies@gmail.com`. The `/u/N/` index is NOT stable — if a console URL bounces to accept-terms/create-developer-account you're on the wrong Google account (e.g. `dzianisvv@gmail.com` hits a ToS gate); use the developer-account chooser to reach VIBE.
|
||||
- **Rebrand (2026-05-30)**: package renamed `ai.opencode.mobile` → `cc.agentlabs.opencode`. A NEW Play Console app is required (package IDs can't be renamed). New app ID: TBD (creation in progress / teammate-owned). First AAB upload for a new app must be MANUAL via UI (Google blocks the Developer API for a new app's first release); CI can publish updates after.
|
||||
- **Rebrand (2026-05-30)**: package renamed `ai.opencode.mobile` → `cc.agentlabs.opencode`. A NEW Play Console app is required (package IDs can't be renamed) — creation NOT yet confirmed (do not record an app ID until verified from a live dashboard URL). First AAB upload for a new app must be MANUAL via UI (Google blocks the Developer API for a new app's first release); CI can publish updates after. CI `packageName` already = `cc.agentlabs.opencode`.
|
||||
- **Legacy app (orphaned)**: `ai.opencode.mobile`, app ID `4975545755653045321` — published v19 to internal track (run 26662900471), superseded by the rebrand.
|
||||
- **Track**: Internal testing (no review required, up to 100 testers)
|
||||
- **Service account**: `playstore-deploy@opencode-mobile-deploy.iam.gserviceaccount.com` (account-level API access already granted)
|
||||
|
||||
Reference in New Issue
Block a user