stock firmware (eui 5.8) without root. play services - 20.18.17
Are you also using nabu casa? do you have the remote toggle enabled? What URL’s are you using to login?
No,Hass installed on rasppbery pi , using external URL, https . From other phone(Redmi note 8 pro) all work.
does this device normally have google play services installed or did you have to install it manually? its possible that its missing android system webview as an actual system app instead of just an app thats installed from the play store.
gapps exist in stock firmware, android system webview - sys app, i can update o remove update only.
are there any HA errors in the log?
Webview info app show me: android system webview real version is 40…I will update the firmware. Sorry 
Fixed my problem. Thankyou.
1 Like
Hello,
Seems that I’m having the same issue on a brand new install. Mobile device (Galaxy S20 Ultra 5G) is on stock firmware, webview is installed and updated (v96.0.4664.92). config does contain default_config:. Tried adding mobile_app: anyway, but to no effect. Can connect via browser on the mobile device (but not mobile_app:). Don’t know what “nabu casa” is, so don’t have it unless it’s a default install option. HA is on a HAOS VM, version core-2021-12-1.
Any recommendations welcome!
Hello! I have my tablet with android 4.2 and it had the error due to the webview. Install chrome and it didn’t fix it, I managed to fix it by installing Opera browser.
Thank you for your response. I was given a Samsung Tab3 that had been used in a special application and would not work with HA. I noticed it did not have google play installed and li had installed in manually and it was missing android webview. You put me in the right direction on finally getting it to work.
Opera browser work for me also.
I already share this post with the solve.
Basically, you need to update/install “Android System WebView” in your device
1 Like
I have several Android Web Views (std., Canary and Beta) and Android Web View Developer installed.
Since today, HA app didn’t work anymore, same symptoms as above.
This thread brought me to the solution:
Switch to Android Web View std. - Canary was selected before and had been updated over night, apparently caused the problem with HA.
Tried on “mxq pro 4k” android box (AOSP), always stuck on initializing.
Android WebViews is installed, with Opera Browser i can login but not with Chrome.
Can’t access full android settings as I get only the “simplified” TV Version.
You need to use Google version of Android system WebView and it needs to be selected as the default WebView. Aosp ships with incompatible WebView usually.
1 Like
Already installed the google version but can’t access the settings where usually it can be selectable as default. Now i’m trying to find some workaround
Just as an update with what worked for me. I needed to ensure I had the latest stable Chrome and Webview apps installed. This was on an older (Android 7.0) device.
Installing the APK from here fixed this issue for me (and other issues I was starting to confront due to the outdate webview on my FireHD10 2019):
https://amazon-system-webview.en.uptodown.com/android/download/101847171
2 Likes
It’s been a while, but I just ran into the same issue on an old Samsung Galaxy Tab E9.6 with lineage os 14.1 (Android 7.1.2). Installed the App but it would get stuck initializing. In Chrome or Edge it worked fine, though. Installing Opera as suggested did not help, also installing WebView didn’t.
What finally solved it for me was enabling the Android developer options (clicking on the build number in the Android settings/system information a couple of times) and then within the unlocked dev options select the Chrome WebView instead of the default one. Since then, App is just working great incl. full screen and always on 
. So, seems in my case Chrome AND WebView AND this setting was the key.
1 Like