关于Google Play商店Open Testing的含义及应用状态从审核转为Open Testing的咨询

Hey there! Let's unpack what's going on with your app's status shift—since this is your first time encountering this, it’s totally normal to be confused.

First, let’s get clear on the basics: Open Testing is Google Play’s public beta testing track. Unlike the Production channel (which is your fully live app for all users), this track lets you share a link with anyone to let them test your app, gather feedback, and iron out kinks before a full production launch. It’s a separate, pre-release space from your live production version.

Why Did Your App End Up Here Instead of Production? #

There are two likely reasons:

• Accidental track selection during submission: It’s super easy to miss this step when publishing for the first time. When you submit your build, Google Play Console asks you which track to send it to—if you accidentally picked Open Testing instead of Production (or didn’t double-check the selection), that’s exactly why your app moved to this status after review.
• Unintended track configuration (less common): If you previously set up auto-promotion rules between tracks (like moving builds from testing to production automatically), a misconfiguration could have routed your build here. But this is unlikely if you didn’t explicitly set up those rules.

Is This Part of Google Play’s Normal Production Flow? #

Nope, this isn’t the standard path for a production release. Normally, when you submit to Production, after passing review, your app would shift to the Production status (live for users, or in a staged rollout if you set that up). The switch to Open Testing means your release was sent to the beta track instead.

How to Fix This #

1. Head to your Google Play Console, go to Release management > Testing tracks > Open Testing to confirm your recent build is here.
2. If it was an accident:
   • Option 1: Stop the Open Testing release (if you don’t want public testers using this version) and resubmit your build to the Production track.
   • Option 2: If the Open Testing build is stable and ready for live users, promote it directly from Open Testing to Production in the Console. This will trigger a quick review for the production rollout, which is faster than submitting a new build.

内容的提问来源于stack exchange，提问作者Peter Palfreeman