Key takeaways
- The Jules VM ships with Java and Gradle; add the Android SDK through a setup script and let Jules snapshot the environment for later tasks.
- Branch protection, required checks and CODEOWNERS for signing and workflow files keep an unattended agent inside safe limits.
- Merging never releases anything – a version tag set by a person starts the signed build and the upload to the internal track.
- Tester reports and pre-launch findings become small Jules tasks; policy declarations and production stay with the account owner.
What runs in the Jules VM – and what does not
Jules works asynchronously on your GitHub repository: you describe a task, approve its plan, and it carries out the work in a short-lived virtual machine before returning a branch or pull request. The Jules environment documentation describes that VM as Ubuntu Linux with tools such as Java, Gradle, Node.js and Python preinstalled. The Android SDK is not on that list, but nothing stops you from adding it.
| Check | Inside the Jules VM | Where else |
|---|---|---|
| Compile, lint, unit tests | Yes, once the SDK is installed | CI on every pull request |
| JVM-based UI tests (for example Robolectric) | Yes | CI |
| Emulator or device tests | Do not plan on it | CI with an emulator, local devices |
| Signed release bundle | Never | Tag-triggered release workflow |
| Real-device crawl | No | Google Play's pre-launch report |
That is a much better position than on iOS, where the same VM cannot build the app at all.
A setup script and snapshot for the Android SDK
In the repository's configuration, Jules accepts an initial setup script. You run it once; if it succeeds, Jules saves a snapshot and starts later tasks from it, which saves the long SDK download on every run. An outline:
# Jules initial setup (outline) – runs once, then snapshotted # - download the Android command-line tools into $HOME/android-sdk # - accept the licences; install platform 36, build tools, platform tools # - point Gradle at the SDK (ANDROID_HOME or an uncommitted local.properties) # - ./gradlew --no-daemon lint testDebugUnitTest # fetches dependencies
When you upgrade the Android Gradle Plugin or add libraries, rerun the script so the snapshot matches the project again. The script prepares a development environment only – no keystore, no passwords, no Play service account.
Talk to an AI Code Engineer about shipping your app to Google Play.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
Guardrails in the repository
An agent you are not watching needs limits that do not depend on it reading instructions correctly. Combine three layers:
- AGENTS.md at the repository root, which Jules reads: the permanent
applicationId,targetSdk36, the Gradle tasks every change must pass, and the rule that new permissions and SDKs are named in the pull request. - Branch protection on
main: required status checks (lint, unit tests,assembleReleaseso R8 problems surface early) and at least one human approval. - CODEOWNERS for the signing block of the Gradle build,
AndroidManifest.xmland.github/workflows/, so changes there always reach the person responsible for releases.
Our process for reviewing agent-generated code fits small teams that receive several agent pull requests a day.
From merged pull request to testing track
Keep merging and releasing separate. A merged Jules pull request is just code on main; a release is a deliberate act:
- A person tags a version on
main. - The release workflow decodes the upload keystore from CI secrets, sets
versionCodeand builds the App Bundle withbundleRelease. - It uploads the bundle to the internal testing track using a Play service account; Play App Signing re-signs it with the key Google holds.
- A person tries the build, then promotes it to closed testing or to production as a staged rollout.
Jules can write and maintain this workflow, like any other code – reviewed through CODEOWNERS. The upload key, its passwords and the service account credentials are created and stored by people. Our fastlane setup guide covers the upload step.
Tester feedback and pre-launch reports as Jules tasks
Jules is at its best with small, well-described tasks, and testing produces exactly those. For each finding, write one task with the Android version and device, the steps, what you expected, what happened and – if there is one – the stack trace from the pre-launch report or Android vitals. Approve the plan, review the pull request, and the fix goes out with the next tag.
If your developer account is a new personal one, this loop also carries you through the mandatory closed test: Google requires at least 12 testers who stay opted in for 14 consecutive days before you can apply for production access. Regular updates during those two weeks, driven by tester feedback, are what a real test looks like. The closed testing playbook has the details.
Policy gates a person signs off
Before production, the account owner confirms the declarations that Jules can inform but not submit:
- Data safety – ask Jules for an inventory of SDKs and data flows, then verify it (Data safety with AI agents).
- Account deletion – inside the app and through a public web page linked in the Play Console.
- Target API level 36 for new apps and updates.
- Google Play Billing for digital goods and subscriptions.
- Sensitive permissions – each one justified and declared where Google asks for it.
Our AI Code Engineers can own this part for you – signing, release workflow, listing, declarations and the review – inside your own Play Console; see the Android submission service. The iOS counterpart, where Jules needs a Mac to check its work, is Jules app to the App Store.
Jules to Google Play checklist
- The Jules setup script installs the Android SDK and the snapshot is current.
- AGENTS.md defines applicationId, targetSdk 36, required Gradle tasks and reporting rules.
- Branch protection requires lint, unit tests, a release build and a human approval.
- CODEOWNERS covers signing configuration, manifest and workflows.
- Only a version tag set by a person triggers the signed build and upload.
- Upload key and service account credentials exist only in CI secrets.
- For new personal accounts: closed test with 12+ testers for 14 consecutive days completed.
- Data safety, account deletion, billing and permission declarations confirmed by the account owner.
Frequently asked questions
Can Jules build Android apps?
Yes. Its Ubuntu VM includes Java and Gradle, and a setup script can add the Android SDK. Jules can then compile, lint and run unit tests. Signed release builds should come from your own CI.
Can Jules upload to Google Play?
It should not hold the credentials to do so. Let Jules maintain the release workflow as code, and keep the upload key and the Play service account in CI secrets that only a tag-triggered workflow uses.
Is it safe to let an async agent work on our production app?
With guardrails, yes: plan approval, branch protection with required checks, CODEOWNERS on sensitive files and releases that only a person can start. The agent proposes, people decide what ships.
Can you set up this release process for us?
Yes. Book a free call and an AI Code Engineer reviews your repository, guardrails and Play Console. We can build the pipeline and handle signing, listing and review in your own account.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.