App Stability Metrics Google Looks For in Closed Testing

The Hidden Test: Android Vitals

When Google enforces the 14-day closed testing rule, they aren't just checking if 12 people opened the app; they are actively monitoring how your code performs on physical hardware.

This data is logged in the Android Vitals section of the Play Console. If your app violates Google's core stability thresholds during the test, your production application will be denied.

Metric 1: Crash Rate

A crash occurs when an unhandled exception forces the app to close immediately.

• The Bad Behavior Threshold: Google flags your app if the user-perceived crash rate exceeds 1.09% across all sessions.
• If your testers constantly crash the app on boot, you must push an update to the closed test track immediately to lower this percentage before the 14 days end.

Metric 2: ANR Rate (App Not Responding)

An ANR happens when the main UI thread of your app is blocked for more than 5 seconds (usually because you are doing heavy network or database work on the main thread instead of a background thread).

• The Bad Behavior Threshold: Google is incredibly strict about ANRs. The threshold is 0.47%.
• ANRs are highly frustrating for users. If your closed testers trigger frequent ANRs on older devices, Google will assume the app is not optimized for public release.

How to Pass the Stability Check

Ensure your 12 testers are using a variety of devices, especially older mid-range phones. If your app runs perfectly on an ultra-fast Pixel 8, but causes an ANR on an older Galaxy A-series device, you need to know that during the closed test, not after you launch.