How to Use Closed Testing Tracks for Android TWA Releases

When publishing a Progressive Web App (PWA) to the Google Play Store using a Trusted Web Activity (TWA), uploading your Android App Bundle (AAB) directly to the production track is highly discouraged. Because TWAs depend on a strict cryptographic handshake called Digital Asset Links, you must thoroughly verify your application in a controlled store environment before going live. Google Play Console provides specific testing tracks to facilitate this process.

Using a Closed Testing Track is the most secure and realistic way to distribute your test builds. It allows you to release your TWA to a select group of alpha or beta testers, verify that the browser wrapper functions without showing a URL bar, test native push notification payloads, and validate deep linking. This step-by-step guide walks you through configuring closed testing tracks specifically for TWA-based Android apps.

Understanding Testing Tracks in Google Play Console

Google Play Console categorises app distribution into four main tracks, each designed for a different phase of the release cycle. Choosing the correct track ensures you can test your code safely without exposing experimental configurations to public search results.

While internal testing tracks are fast to deploy, closed testing tracks are superior for simulating the actual end-user experience because they trigger the exact same security checks, key-signing structures, and package validation mechanisms used in production.

Setting Up a Closed Testing Track

To begin, navigate to your Google Play Console dashboard and select your application. Under the Release section in the left-hand navigation menu, select Closed Testing. Click on the Create Track button in the upper right-hand corner. You will be prompted to name your track, which is typically called Alpha, Beta, or QA.

Once the track is created, click on Manage Track to begin configuration. You must define who can access this track. Google Play Console allows you to manage testers using email lists. You can upload a CSV file of email addresses or enter them manually. Alternatively, you can use Google Groups to manage your tester pool, which is ideal for larger beta groups. Ensure that your testers are signed into their Android devices with the exact email address added to your tester list.

Managing the Digital Asset Links Trap in Test Tracks

The single most common issue developers face when deploying a TWA to a Closed Testing Track is the sudden appearance of the browser URL bar. During local development, you likely configured Digital Asset Links using your local debug signing key. However, when you upload your AAB to Google Play Console, Google Play App Signing strips your local key and signs the bundle with a unique App Signing Key maintained by Google.

Because the SHA-256 fingerprint changes, the cryptographic handshake between your web application and the installed Android app fails. Consequently, the Android operating system treats the app as a standard browser window and displays the URL bar. To fix this in your Closed Testing Track, you must retrieve the Google Play App Signing certificate fingerprint.

Go to Setup in the left-hand menu, click on App Integrity, and locate the App Signing tab. Copy the SHA-256 fingerprint listed under the App Signing Key Certificate section. You must add this specific SHA-256 fingerprint to your web server's .well-known/assetlinks.json file, alongside your local debug fingerprint. This guarantees that your testers will experience the seamless, full-screen, native look of your TWA wrapper without the browser URL bar interface.

Inviting and Onboarding Your Testers

After uploading your TWA release bundle to the closed track and submitting it for review, Google will verify the package. Once approved, you must share the opt-in URL with your designated testers. Under the Testers tab in your Closed Testing Track configuration, you will find a Web URL that allows testers to opt into your test program.

Your testers must follow these steps to install the app:

• Open the provided opt-in URL on their Android device.
• Click the button to accept the testing invitation.
• Click the download link, which routes them to the private Google Play Store listing.
• Install the application as they would any standard Android app.

If your testers report seeing the URL bar on launch, double-check that your assetlinks.json file is correctly deployed on your production web server and is publicly accessible without redirects or authentication barriers.

How to Transition from Closed Testing to Production

Once your testers have thoroughly validated the application, you do not need to rebuild or re-upload your AAB to move to production. Google Play Console permits you to promote your closed testing release directly to the production track.

To do this, navigate to your Closed Testing track, locate the successful release build, and click Promote Release. Select Production from the dropdown menu. This workflow ensures that the exact binary that was successfully validated by your testers is what gets distributed to the public, minimising the risk of unexpected runtime anomalies or certificate mismatches. Confirm the rollout parameters and submit the release for final production review by Google.