You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Google Play pre-launch report. The built in open check. Open Source Patterns
#1618
When an app bundle is uploaded to a testing or production track, Google installs it on real devices in a test lab, launches it, and crawls it for several minutes. The pre-launch report is the closest thing Google has to an automated pre submission check, and it is free to every developer. Treat a clean pre-launch report as a release gate.
Area
What it finds
Stability
Crashes captured by the automated crawl across many real devices
Compatibility
Use of APIs that are not in the public Android SDK
Security and privacy
Vulnerabilities in the app and its SDKs that an attacker could exploit
The lesson. Run the closed testing track and read the pre-launch report before production. It catches device specific crashes, non public API use, and security holes that a single device test misses.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
When an app bundle is uploaded to a testing or production track, Google installs it on real devices in a test lab, launches it, and crawls it for several minutes. The pre-launch report is the closest thing Google has to an automated pre submission check, and it is free to every developer. Treat a clean pre-launch report as a release gate.
Source. Pre-launch report help and understand your pre-launch report.
The lesson. Run the closed testing track and read the pre-launch report before production. It catches device specific crashes, non public API use, and security holes that a single device test misses.
Source section. OPEN-SOURCE-PATTERNS.md, Google Play pre-launch report. The built in open check.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions