fix(android): use draft status for Play Store uploads

[raivieiraadriano92]

Summary

Nightly Android builds were failing at the Google Play upload step with: Only releases with status draft may be created on draft app.

The upload script was using status: 'completed' for internal track releases, but Google Play rejects non-draft releases until the app's Console setup is fully complete (store listing, content rating, target audience, etc.).

This reverts the release status to 'draft' to unblock CI. Once the Play Console setup is finalized, the commented-out line can be restored to auto-rollout to testers.

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk: a one-line change in the Play upload script that only affects CI/release automation behavior. It may delay internal tester rollout until the status is reverted, but does not impact runtime app code or data handling.

Overview
Fixes Google Play upload failures by forcing non-production track releases created by scripts/upload-to-play.cjs to use status: 'draft' instead of auto-marking internal releases as completed.

Adds an in-file note explaining that auto-rollout requires completing Play Console app setup, and that the previous conditional status can be restored once setup is finished.

^{Reviewed by Cursor Bugbot for commit b897c8c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Semgrep Security Scan

No security issues found.

[github-actions]

PR Metrics

Metric	Value
Lines changed (prod code)	+4 / -1
JS bundle size (gzipped)	🟢 1.02 MB → 1.02 MB (-5.1 KB, -0.5%)
Test coverage	🟢 70.57% → 70.57% (+0.0%)
Load time (preview)	Preview not ready — Render deploy may have timed out

Updated Tue, 21 Apr 2026 09:01:37 GMT · run #1060