Google Play on-device Android containers policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps that simulate Android environments or run other Android apps inside a container.
An app can use REQUIRE_SECURE_ENV to say it must not run inside an on-device Android container. If your app provides that container, Google requires you to honor the flag.
What to check
Inspect the manifest of each app before loading it. Check import flows, updates, cloned apps, and older versions. The restriction also covers proxying device APIs to make an app appear installed inside the container.
Don’t treat a failed launch as something to work around by stripping the flag or selecting an older version without it.
How to address the rejection
Block loading of apps that declare REQUIRE_SECURE_ENV. Remove proxy behavior or fallback paths that defeat the protection, and explain to users why the app can’t run in the container.
Test fresh imports and apps already stored in your container. An installation-time check alone may miss a later update. In your response, identify the manifest check and show that flagged apps stay blocked throughout the supported loading paths.
Messages this guide can help with
On-device Android containers; On-device Android containers policy violation; On-device Android containers rejection; On-device Android containers denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: On-device Android containers Checked 22 September 2026