Bitrise Immerse

Pipeline Stages

Sending your Google Play Console Review

Submit your Android app for Google Play Console review and configure release settings in Rollout.

The Google Review stage is the Android equivalent of the App Store Review stage. Here, you submit your Android build to Google Play Console for review before releasing it to production.

To send your app to Google Play Console review, you need to have the Release Manager role for your connected app.

Prerequisites

Before you can submit for Google Play review:

  • All six approvals must be Approved (see Approvals)
  • Your Google Play Console configuration must be complete (see Settings)
  • Your release candidate must have been uploaded to Google Play (see Google Play Upload)

Submitting for Review

  1. Open the Google Review stage

    Navigate to your version’s pipeline view and expand the Google Review stage card.

    google-review-ready

    The Google Review stage in Ready for Review state

  2. Configure release settings

    Review the release settings section:

    • Staged Rollout — Toggle on/off. When enabled, your app rolls out gradually to users over 7 days in percentage-based stages instead of all at once.
    • Release Type — Choose between a full release to all users or a staged rollout.

    google-release-settings

    Google Play release settings with staged rollout options

  3. Review and update release notes (optional)

    Review the release notes that will appear on the Google Play listing. You can edit these before submission — the change only affects the current release, not your default presets.

  4. Submit for review

    Click “Send for Review”. The build is submitted to Google for review.

Tracking Review Status

After submission, the stage card shows the current Google Play review status:

StatusMeaningWhat to Do
In ReviewGoogle is currently reviewing your appWait — Google reviews typically take a few hours to several days
ApprovedGoogle has approved your appMove to the Google Release stage
RejectedGoogle has rejected your submissionReview the rejection reason and address the issues

If Your App Is Rejected

If Google rejects your submission:

  1. Review the rejection reason

    Read the rejection details shown in the stage card. Google provides specific policy violations or issues with each rejection.

  2. Determine the type of fix needed

    • Code changes needed — Go back to the Release Candidate stage to select a new build
    • Metadata changes only — Update via the release notes editor

  3. Make corrections

    Address the issues Google identified.

  4. Re-submit for review

    Submit for review again after corrections are made.

Common rejection reasons include: policy violations, crashes or ANRs detected during review, incomplete store listing information, and privacy policy issues.

Troubleshooting

“Send for Review” button not available:

  • Ensure all six approvals are in Approved status
  • Verify Google Play Console configuration is complete
  • Confirm the release candidate has been uploaded to Google Play

Review taking longer than expected:

  • Google Play reviews can vary from a few hours to several days
  • New apps and apps with significant changes may require longer review times
  • Check Google Play Console directly for any additional information requests

What’s Next