If your app is built using TWA/PWA and opens directly in Chrome, this is one of the biggest reasons for closed testing failure.

Many developers complete 14 days but still don’t get Production Access.

How to identify this issue

• Your package name often ends with .twa or .pwa
• App opens directly in Chrome (not inside a native screen)
• Usage tracking shows 0–1 seconds on most devices

Why this causes rejection

Google expects in-app user engagement.
If your app is just a wrapper opening Chrome, there is no real activity tracked inside the app.

Even if testers use it daily, it may still look like no usage.

The fix (this works)

You must add at least one native Android screen.

Simple solution:

• Add a Welcome / Onboarding screen
• Add a “Get Started” button
• On click → open your website/TWA

Now your app becomes:

• Native + Web
• Trackable by Google
• Eligible for approval.

Alternative (temporary)

Convert your app to WebView until you get Production Access.
After approval, you can switch back to TWA.

Important

If you don’t fix this:

• Testing data will remain very low
• Google may reject again
• You may have to restart the 14-day process

Final tip

Before continuing testing, always check:

• Is usage being tracked properly?
• Is there at least one native screen?

Fixing this early can help you get Production Access on the first attempt.