Deploy & App Stores
Publishing a ChatGPT Codex App on Google Play
Codex can cover most of an Android release: because Gradle runs on Linux, a Codex cloud task can often build and test the Android project before opening a pull request, while the CLI handles local emulator debugging. You still manage the signing keys, the Play Console listing, the Data safety form and, for new personal accounts, the 12-tester closed test.
What can Codex do for Android that it cannot do for iOS?
Codex can usually run Android builds in its own environment, because the Android SDK and Gradle work on Linux. That means a cloud task can make a change, run ./gradlew assembleDebug or unit tests and only then open the PR.
Whether the SDK is available depends on your Codex environment setup, so configure it once with the Android command-line tools and a JDK and document that in AGENTS.md.
- Gradle builds and unit tests inside cloud tasks
- Lint checks for permissions and target SDK
- CI workflows for signed release bundles
How should AGENTS.md describe the Android build?
List the exact commands and the immutable values so Codex never improvises them. The applicationId, signing approach and target SDK policy belong at the top.
Also tell Codex what to verify before opening a PR, for example that the debug build compiles and that no new permissions appear in the merged manifest without a feature that needs them.
- applicationId: fixed, never change
- Build: npm ci, npm run build, npx cap sync android, ./gradlew bundleRelease in CI only
- Secrets: keystore and Play service account JSON only via CI secrets
- Back button, insets and notification permission handled on every screen
How do you produce and sign the .aab?
Release signing belongs in CI with secrets, not in Codex's environment. Let Codex write the Gradle signing config and the workflow; you create the upload keystore and add it as a CI secret.
Enroll in Play App Signing so the app signing key is protected by Google and only the upload key lives in your pipeline.
- Create the upload keystore locally and store it encrypted in CI secrets
- Codex task: add signingConfigs that read from environment variables
- Codex task: create a workflow that builds bundleRelease on tags
- Upload the very first .aab manually in Play Console
- Codex task: add fastlane supply or Play Developer API uploads for later releases
How do you plan for the closed testing requirement?
New personal developer accounts must run a closed test with at least 12 testers opted in for 14 consecutive days before production access. Start it as soon as the first stable build exists.
Use Codex to accelerate the feedback loop: turn tester reports into issues, assign each to a cloud task and ship fixed builds to the closed track during the test. That record of iteration helps when you answer Google's production access questions.
How do you complete the Data safety form for a Codex-built app?
Ask Codex to generate a data inventory from the code: every network endpoint, SDK and stored field. Then a human maps it to Google's Data safety categories and submits.
If the app sends user input to the OpenAI API or another model provider, that is data sharing or processing you must disclose. Keep API keys on your server; a key embedded in an Android app can be extracted from the bundle within minutes.
- Account info, app activity, user content, diagnostics
- Third-party SDKs: Firebase, analytics, crash reporting
- Account deletion path in-app and via web link
Which Android features are worth assigning to Codex?
Assign isolated, testable features: Firebase Cloud Messaging push, Android App Links with assetlinks.json, Play Billing for digital goods and in-app updates. Each one fits a single cloud task and PR.
Keep UI polish such as edge-to-edge layouts in local CLI sessions where you can see the emulator, because visual issues are hard to judge from a diff.
How do you make the process repeatable?
Combine AGENTS.md, CI and a fixed release checklist so every Android release looks the same. neooutput helps teams set this up through agentic coding workshops and hands-on work by our AI Code Engineers, and appsubmitter.io supports the store submission process.
If maintaining a native Android project is more than the product needs, WebViewGold is a no-code option that turns the deployed web app into native Android and iOS apps with configurable push notifications, deep links and an offline screen, while Codex keeps improving the web code. Plan real native value into the wrapper; Apple's guideline 4.2 in particular rejects apps that are just a website.
Frequently asked questions
Can Codex publish to Google Play automatically?
It can write the automation, and CI can upload builds via the Play Developer API. The first upload, account setup and policy declarations should be done manually by you.
Does the 12-tester rule apply to my account?
It applies to personal developer accounts created after Google introduced it in late 2023. Organization accounts are currently exempt but need business verification.
Should I use Expo with Codex?
Expo works well if you build mobile-first; EAS Build and EAS Submit handle Android builds and uploads from the cloud. Capacitor is better if you are reusing an existing web app.
What target API level do I need?
Google requires new apps and updates to target a recent Android API level, and the requirement rises roughly once a year. Check Play Console's current requirement before each release.
