Submit a Google Play release with working review access

You’ve saved the release, but Play Console says changes haven’t been sent for review. Saving a bundle or form can leave them waiting in Publishing overview. Finish the release and App content answers, then send the pending changes from there.

Confirm that account verification and any required production access are complete. Have an accepted bundle, store listing, rating, privacy policy, Data safety answers, and all required declarations ready.

Give the reviewer access that works

Clear the dashboard’s required setup tasks and check App content for unfinished declarations. Under the sign-in or app-access task, supply reusable credentials that work regardless of location and stay available during review.

Write clear English instructions for every restricted feature. For a dedicated review account, provide a reliable way past one-time-code or MFA obstacles while keeping normal users’ authentication secure.

Include access to paid or subscription areas. Supply a stable sample QR code or other supporting information if the reviewer needs it. Try the account yourself and confirm that it opens the relevant features.

Send the release and content changes

1. Prepare the release in the track you intend to use. Check the bundle, release notes, countries, and validation errors.
2. Open Publishing overview and review the pending changes.
3. Choose Send for review when required.
4. Confirm that the intended changes are in review. Check whether approval will publish them automatically or leave them waiting under managed publishing.

If the release won’t move forward

Check the release and the App content tasks separately. The release can be ready while a required declaration is still incomplete.

If a reviewer can’t sign in, fix the access route and test it yourself before replying. Sending the same credentials again is unlikely to help.

If production is unavailable, check whether you still need production access. That’s a separate step from app review.