Closed testing guidance
TWA apps and closed testing in TestFlow
TestFlow does not accept Trusted Web Activity (TWA) builds. Convert to a WebView app with the same package name before you submit a campaign. Google Play still decides Production Access.
Why TWA submissions are paused
A TWA is a thin Android wrapper, often produced by PWABuilder or Bubblewrap, that opens your website in Chrome. Tester taps then happen in Chrome, not inside your app process. Google Play’s review looks at usage of the app itself, so a TWA campaign can look idle even when testers used the site. TestFlow pauses those submissions so you do not spend a 14-day closed testing window on a wrapper that may not be measurable.
What to submit instead
Rebuild as a WebView app: the same website loads inside your own app. Keep the exact package name, raise the version code, and sign with the same upload key so Google Play treats it as an update. Upload that build to the same closed testing track. The 14-day opt-in clock follows testers, not the binary.
Do not rely on a “WebView fallback” setting in PWABuilder or Bubblewrap. On phones with Chrome the app still runs as a TWA.
After you convert
- Install a test APK and confirm the site loads inside the app, not as a Chrome hand-off.
- Upload the AAB to the existing closed testing track in Play Console. Do not create a new app.
- Return to TestFlow and submit the WebView build as a normal campaign.
After completing the applicable testing requirements, you can submit your Production Access application through Google Play Console. Google makes the final decision.