forceFallbackStrategy about android-browser-helper HOT 6 CLOSED

Android TV doesn't come with a browser installed and Chrome doesn't have an Android TV version.

So, my expectation is that, if running on Android TV, it wouldn't find a browser that supports TWA and that would trigger a fallbackStrategy, without the need to force it.

Having said that, the default CCT strategy won't work (as there isn't usually a browser installed), and the developer would have to provide their own WebView fallback that is used to navigate both internal and external links (a modified version of this demo).

Can you provide:

1. More details on the browser (or browsers) installed on the TV
2. The configuration being used on AndroidManifest, build.gradle or any other classes used on the Android implementation.

from android-browser-helper.

[google translate]
that's right, after installing the application on android tv, webview started, but when I was wondering if the browser is installed, how the application behaves, I installed chrome on android tv, and it’s not displayed in the webview, but chrome

1.chrome beta 80.0.3987.78
2. everything is like in the demo twa-webview-fallback

[orig_ru]
всё верно, после установки приложения на андроид тв запустился вебвью, но когда мне стало интересно если будет установлен браузер то как приложение себя поведет, установил я хром на андроид тв, и уже не в вебвью отображается, а хроме

1. хром бета 80.0.3987.78
2. всё как в демо twa-webview-fallback

from android-browser-helper.

How was Chrome installed into the Android TV? AFAIK, it's not officially supported, which may lead to unexpected behaviours.

re: the twa-webview-fallback demo, won't work correctly on Android TV as well without modification, as this section tries to launch a CCT when navigating outside the app domain.

from android-browser-helper.

installing apk

from android-browser-helper.

Closing this, as supporting Android TV is not a goal at the moment.

from android-browser-helper.

@andreban that's unfortunate, we have a multiscreen PWA that would benefit from this.
If I read correctly we can still deploy the bubblewrap generated AAB/APK to android TV and it will fallback to webview, correct? as long as the PWA supports linear navigation it should work, or do we need to modify something in the manifest to make it work for Android TV?

from android-browser-helper.