The most common rejection: policy 4.3
Policy 4.3 — minimum functionality — is the number-one rejection cause for website-to-app wrappers. The fix is structural: use a TWA on a proper PWA, not a raw WebView.
Pre-submission checklist
- Use a TWA via Bubblewrap (or SaaSToStore) instead of a raw WebView
- Valid web manifest with icons, name, theme color,
display: standalone - Service worker that handles offline gracefully (at least an offline page)
- Digital Asset Links pointing from your domain to the app's signing fingerprint
- Privacy policy URL accessible without login, hosted on your domain
- Data safety form filled honestly — wrong answers trigger rejections
- Original icon (no copyrighted material) at 512×512
- Feature graphic at 1024×500 with no app-store mockups in it
- At least 2 phone screenshots showing actual app content
- Content rating questionnaire completed
What to do if you get rejected
Read the rejection email carefully — Google cites the exact policy. Fix the underlying cause (not just the symptom), increment your version code, push a new .aab, and resubmit. Most rejections are cleared on the second try.