TWA shows "Running in Chrome" despite matching assetlinks.json and asset_statements in APK

[UMMEMIGRATION]

Describe the bug
My TWA app never opens in standalone/full-screen mode — Chrome always shows "Running in Chrome" with visible browser UI, even though I've verified every piece of the Digital Asset Links chain matches.

What I've verified:

1. SHA256 fingerprint matches exactly between keystore, twa-manifest.json, and live assetlinks.json
2. Google's official Digital Asset Links validator confirms SUCCESS
3. Decompiled the built APK's AndroidManifest.xml — the embedded asset_statements string exactly matches the live assetlinks.json, including both handle_all_urls and use_as_origin relations
4. assetlinks.json is served correctly at https://food-at-door.vercel.app/.well-known/assetlinks.json
5. Tried: uninstall + clear Chrome cache/data + reinstall, full phone restart, completely fresh Bubblewrap build from scratch

Result: Still shows "Running in Chrome" banner every time, app never enters standalone mode.

Environment:

• Android device: realme P1 Pro 5G, realme UI 7.0
• Site: https://food-at-door.vercel.app
• Package: app.vercel.food_at_door.twa

To Reproduce

1. Install signed TWA APK on device
2. Open the app
3. See "Running in Chrome" banner, full browser UI visible

Expected behavior
App should launch in standalone full-screen mode with no browser UI, matching the verified Digital Asset Links configuration.
You

[aulalghifary-arch]

TWA address bar tidak pernah hilang meskipun Digital Asset Links terverifikasi 100% valid (Bubblewrap / PWABuilder cloud build)

Ringkasan masalah

Aplikasi TWA yang di-generate lewat PWABuilder (menggunakan Bubblewrap di baliknya) selalu tampil dengan toolbar browser (tombol close "X", domain, ikon share, menu titik tiga — gaya Custom Tab) alih-alih fullscreen standalone. Ini terjadi secara konsisten di banyak perangkat fisik yang berbeda, termasuk perangkat yang baru pertama kali install aplikasi ini (belum pernah ada riwayat/cache terkait sama sekali), meskipun seluruh prasyarat Digital Asset Links sudah diverifikasi benar berulang kali dari berbagai sisi.

Gejala tambahan: Play Billing / Digital Goods API juga tidak bisa dipanggil sama sekali (muncul pesan fallback buatan aplikasi sendiri, menandakan bridge Play Billing tidak tersedia) — konsisten dengan app yang tidak dikenali sebagai TWA terverifikasi.

Detail aplikasi

• Package name: io.github.aulalghifary_arch.twa
• PWA source URL: https://aulalghifary-arch.github.io/Buku-Kas-Aul-Gen2.5/
• Host domain untuk Digital Asset Links: aulalghifary-arch.github.io (root domain, PWA di-host di subpath repo terpisah)
• Tool: PWABuilder (pwabuilder.com), cloud build service → Bubblewrap CLI di baliknya
• Distribusi: Google Play Console, Closed Testing track, format AAB dengan Play App Signing

Yang sudah diverifikasi BENAR (sudah dicoret dari daftar kemungkinan penyebab)

1. assetlinks.json di https://aulalghifary-arch.github.io/.well-known/assetlinks.json — JSON valid, berisi dua sha256_cert_fingerprints (upload key DAN Play App Signing key), package_name cocok persis.
2. Google's official Digital Asset Links tester (developers.google.com/digital-asset-links/tools/generator) — hasil: "Success! Host https://aulalghifary-arch.github.io grants app deep linking to io.github.aulalghifary_arch.twa." untuk fingerprint App Signing Key.
3. Play Console → Dilindungi dengan Google Play → Penandatanganan aplikasi — App Signing Key SHA-256 dikonfirmasi konsisten, cocok persis dengan yang ada di assetlinks.json.
4. GitHub Pages tidak memblokir .well-known — file .nojekyll sudah ditambahkan di root repo aulalghifary-arch.github.io, dikonfirmasi file bisa diakses langsung (bukan 404) via browser di berbagai device.
5. Instalasi murni via Play Store — dikonfirmasi lewat link closed testing resmi (play.google.com/store/apps/details?id=io.github.aulalghifary_arch.twa), bukan sideload APK.
6. Rilis closed testing sudah fully processed (bukan stuck di processing) — dikonfirmasi status "Tersedia untuk penguji terpilih" di Play Console.
7. Android system-level "Supported web addresses" (Setelan → Aplikasi → [App] → Buka secara default) menampilkan domain terkait, toggle sudah diaktifkan manual — tidak ada perubahan.
8. Versi Chrome up-to-date — dikonfirmasi 150.0.7871.124 di salah satu device yang bermasalah, jauh dari outdated.
9. manifest.json PWA — "display": "standalone" (bukan "browser"), jadi bukan soal display mode.
10. Build log PWABuilder menunjukkan proses berjalan normal tanpa error:

Generating app package for https://aulalghifary-arch.github.io/Buku-Kas-Aul-Gen2.5/
Creating signing information...
Using Bubblewrap to generate app package...
Creating Trusted Web Activity (TWA) project...
Building the app package with Gradle...
Signing APK...
App package signed successfully
Generating asset links...
Digital Asset Links file generated at .../assetlinks.json
Building App Bundle...
App bundle built successfully.
Successfully created app package for https://aulalghifary-arch.github.io/Buku-Kas-Aul-Gen2.5/

11. Uninstall + reinstall bersih, clear cache Chrome, clear cache Google Play Services, restart perangkat penuh — semua sudah dicoba, tidak ada perubahan.
12. Reproduksi di banyak perangkat berbeda — bukan hanya di satu device milik developer (yang sudah dipakai berulang kali untuk testing), tapi juga di perangkat tester baru yang instalasi pertamanya langsung dari Play Store, tanpa riwayat apa pun sebelumnya.

Yang belum sempat diverifikasi

• Isi mentah AndroidManifest.xml / string resource asset_statements di dalam APK/AAB yang di-generate — tidak bisa diperiksa langsung karena proses build dilakukan lewat cloud service PWABuilder (bukan Bubblewrap CLI lokal), sehingga tidak ada akses ke source project Android sebelum di-package.
• Output adb shell pm get-app-links io.github.aulalghifary_arch.twa dari perangkat asli — developer tidak memiliki komputer, saat ini sedang mencoba pendekatan lewat Termux + Android Wireless Debugging (localhost ADB) untuk mendapatkan data ini.

Pertanyaan untuk komunitas

1. Apakah ada known issue di mana APK/AAB hasil generate PWABuilder cloud service selalu fallback ke Custom Tabs UI (address bar terlihat) meskipun Digital Asset Links terverifikasi valid 100% dari sisi server (dikonfirmasi lewat tool resmi Google)?
2. Apakah ada field di twa-manifest.json (misalnya fallbackType, enableNotifications, atau lainnya) yang mungkin di-set secara tidak terduga oleh PWABuilder cloud build, yang tidak terlihat/tidak bisa diedit developer lewat UI PWABuilder biasa?
3. Apakah hosting PWA di subpath (username.github.io/repo-name/, bukan domain root langsung) sambil mendaftarkan host sebagai domain root (username.github.io) punya known issue tertentu terkait TWA verification, meskipun origin (scheme+host) yang diverifikasi Digital Asset Links seharusnya sama?

Terima kasih sebelumnya — sudah menghabiskan waktu cukup lama untuk exclude semua kemungkinan penyebab di sisi konfigurasi developer, jadi kemungkinan besar ini terkait bug/edge-case di tooling. Senang membantu dengan info tambahan atau melakukan test lanjutan kalau dibutuhkan.

[JudahGabriel]

Just to be clear, the first time your run a PWA, Android may show "Running in Chrome". But it should not show the browser address bar if your asset links are correct.

[Rorrorror]

Did you get the fingerprint from google play store console? As that is the fingerprint key you should use.

[aulalghifary-arch]

Yes, I got it. But now I've migrated to Android native and added kotlin Pada Kam, 23 Jul 2026, 12.24 AM, Rorrrorror ***@***.***> menulis:

…

*Rorrorror* left a comment (GoogleChromeLabs/bubblewrap#1045) <#1045 (comment)> Did you get the fingerprint from google play store console? As that is the fingerprint key you should use. — Reply to this email directly, view it on GitHub <#1045?email_source=notifications&email_token=CFF55LCP765IRASYMNSRHH35GD2EDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUHEZDQNRZG4ZKM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5049286972>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFF55LH2IUUG7D5NEI5XWXD5GD2EDAVCNFSNUABFKJSXA33TNF2G64TZHMZDEMBUGQ4DMMJQHNEXG43VMU5TIOBUHE4DOMBRGYZKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CFF55LALFJIWEVELQ7SIKBD5GD2EDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUHEZDQNRZG4ZKM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/CFF55LFJCSLEPKR6RCZF3ML5GD2EDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBUHEZDQNRZG4ZKM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>