App keeps opening in system browser

[toniengelhardt]

Describe the bug

I received the following review on Google Play:

The user reports that the device always opens the app in Flyme browser, which apparently is the system default browser (and cannot be deleted), even though he has set Opera as the default browser, which should be PWA compatible?

To Reproduce

Can not reproduce. Other users with the same Android- and app version seem to have no problems.

Expected behavior

If the app says that it is available for the device in the PlayStore, it should always work as native experience.

Smartphone

• Device: Meizu M5
• System default browser: Flyme v 8.5.110-2021020110
• User default browser: Opera (unknown version)

[andreban]

AFAIK, Opera doesn't support Trusted Web Activity, so that may be the issue. This is the first time I hear about Flyme - I couldn't find it on Google Play. Does it support Trusted Web Activity/

[toniengelhardt]

I don't think so, it's also the first time I'm hearing about it. It seems to be the default browser of Meizu phones. What I'm a bit worried about is that users go to the PlayStore and download the app, but then it just doesn't provide a native experience if they don't have Chrome or Brave installed, which apparently leads to negative ratings.

I'm wondering if it would be possible to check if a TWA compatible browser is installed from the PlayStore and if not display a note saying "this app requires Chrome" or something, or not let the user install it at all, like when the app is not listed in your country?

[andreban]

I'm wondering if it would be possible to check if a TWA compatible browser is installed from the PlayStore and if not display a note saying "this app requires Chrome" or something, or not let the user install it at all, like when the app is not listed in your country?

The TWA already checks for a compatible browser. If no compatible browser is found, there are two fallback options:

• customtabs: Uses a Custom Tab as the fallback and, ultimately, a standalone browser if one is not available.. ensures compatibility with the web platform and that the web content will work as expected, but shows the navigation bar (default).
• webview: Uses a WebView implementation as the fallback. It renders the content in fullscreen, but comes with the drawback that parts of the web app may not work as expected. I'd recommending testing your app using this fallback before deploying a version with the WV fallback enabled.