opencode-mobile/.tasks/14/design.md at 2da0fdf109469c897d52e0898488f24054f9f2a1

Files

engineer 6985e74965 docs(tasks): rebrand-cc-agentlabs ownership audit trail

Rename verified: HEAD builds cc.agentlabs.opencode (build green) and the
app launches at runtime under the new package. CUA session goal blocked
by CI env (no opencode server) -> issue #15.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-05-30 05:05:35 -07:00

1.3 KiB

Raw Blame History

Problem

Service account lacks Play Console API access. CI can build+sign AAB but upload fails.

Goal

First AAB published to Play Store internal testing track via CI.

Success Metric

publish-play-store.yml workflow completes successfully — AAB uploaded to internal track.

Current State

App created in Play Console (ai.opencode.mobile, ID: 4975545755653045321)
Service account exists: playstore-deploy@opencode-mobile-deploy.iam.gserviceaccount.com
CI workflow builds AAB with release signing ✅
Upload fails: "The caller does not have permission"
User is currently on Play Console API access page in Chrome

Proposed Design

User grants service account access in Play Console (they're on the page now)
Re-trigger publish-play-store.yml workflow
Monitor until AAB uploads successfully

Alternatives Considered

Manual upload via Play Console UI — rejected (not repeatable, defeats CI purpose)
Use different auth mechanism — rejected (service account is standard approach)

Risks & Open Questions

Risk: Service account might need specific permissions (Admin vs Release Manager) Mitigation: Grant Admin initially, can restrict later

Touched Surface

No code changes needed — this is a permissions/config task
.github/workflows/publish-play-store.yml already correct

1.3 KiB Raw Blame History