[baba-dev]

P0: First Google Play Internal Testing build crashes at launch — reproduced and fixed

Owner confirmed that Play-installed com.bababuilds.menuminute immediately closes when tapping Open. The temporary (unreviewed) listing title and Android icon are normal first-review placeholders.

Exact diagnosis

First emulator run #42804640519 reproduced the failure:

FATAL EXCEPTION: main
Process: com.bababuilds.menuminute
Unable to start activity com.google.androidbrowserhelper.trusted.LauncherActivity
Caused by: java.lang.IllegalArgumentException:
Component class com.google.androidbrowserhelper.trusted.ManageDataLauncherActivity
does not exist in com.bababuilds.menuminute

The upstream LauncherActivity always calls ManageDataLauncherActivity.addSiteSettingsShortcut while starting, which requires the activity to be declared in the manifest. Our app had omitted it.

Fix

• Register com.google.androidbrowserhelper.trusted.ManageDataLauncherActivity in AndroidManifest.xml with a site-management URL; make it non-exported and point the application's manage-space entry at it.
• Keep the same TWA launcher URL, Digital Asset Links statement, Play Billing service, signing config and existing Google Play package ID.
• Add a regression test ensuring the companion activity and required metadata remain present.
• Add an API 35 Google Play emulator workflow that boots the APK and captures adb logcat Java fatal exceptions. It fails when the launcher crashes, preserving logs for review.

Release

• No production web/API code is altered, and no signing secrets are accessed in PR CI.
• Do not promote the current Play internal build. After new emulator smoke + 19 CI jobs pass, merge, verify auto-generated versionCode > 4 signed AAB, upload to Play Internal testing and check startup on the same phone.
• A clean emulator debug build does not prove Play signing DAL fullscreen on real devices. Verify that separately.

Tracks #340.