Uncaught error from Chrome WebView 130.0.6723.107 on Android 14

Mobile Apps Home Assistant Companion for Android
1

Hi all,

Background

  • I am running HAOS on a Pi5. Recently I moved my entire HA installation (fresh install) to a NVMe (so there is no SD card inserted anymore).
  • I changed the boot order by installing the Raspberry Pi 5 Bootloader (NVMe/USB Boot) on a SD card and booting the Pi with the SD inserted.
  • After turning the Pi off. I installed the NVMe, started the Pi and started off with a fresh installation.
  • Before I created this fresh installation, I had HA running on the same Pi with just the SD, and at some point on a SD/NVMe combination.

I have a lot of stability issues and I can’t figure out what is causing the problem. Which is why I started on a fresh install. I will be adding add-ons/integrations after everything is running smoothly.

The only add-ons I am using right now is DuckDNS, NGINX, Visual Studio, File Editor. But I’m not seeing anything in their respective logs.

Problem

After installation on just the NVMe, I have thes errors shown below. I am not entirely sure when I get these. Since there is no furthere information, I can’t figure out what is going on here.

I have a Pixel 5 and am running Android 14, so I’m sure it is my app that is causing the log entry. There are no updates available (for the app, nor any of the HA components).

Do you guys have an idea?

2024-11-12 14:07:52.857 ERROR (MainThread) [frontend.js.modern.202411062] Uncaught error from Chrome WebView 130.0.6723.107 on Android 14
Script error.
null
@:0:0

2024-11-12 14:07:56.605 ERROR (MainThread) [frontend.js.modern.202411062] Uncaught error from Chrome WebView 130.0.6723.107 on Android 14
Script error.
null
@:0:0

2024-11-12 14:46:57.707 ERROR (MainThread) [frontend.js.modern.202411062] Uncaught error from Chrome WebView 130.0.6723.107 on Android 14
Script error.
null
@:0:0

2

I can’t help you fix your problem, but maybe I can help you narrow down your issue:

  • Do you have another device (laptop/PC) you can try to access HA on which does not run Android 14?
  • If not, do you still get the same issue when using a browser on your phone instead of the app?
3

Hi ShadowFist,

First of all, thank you for thinking along.

  • Yes. I do have other devices (non-android) that I (can) use.
  • I do not get any errors whilst using those devices.

The weird thing is, I don’t allways get these errors. Just every once in a while I see some popping when I check into my logs (which I’m checking often, because of the earlier mentioned stability issues which I’m trying to resolve).

The error I posted is in the frontend.js.modern it seems, which I’m guessing points somewhere into core/homeassistant/components/frontend at dev · home-assistant/core · GitHub but I cannot find anything related.

4

Great to hear it only seems limited to one device.

I’m crap at front end stuff, so humour me. Can you try accessing HA on your same phone using the browser instead of the app for a fixed period of time (a couple of days)? Do the errors disappear when you do that?

I’m suspecting it’s something as stupid as the app cache. Clearing that out once you narrow it down to an app issue should fix that.

5

Isn’t it so that the app & browser are both using webview?

6

Could be. I should have recommended checking for android webview updates in the play store as a first step.

Good catch!

7

I have experienced issues with webview - on an older version of Android - when webview was a recent version.
I think @dshokouhi might be able to shed some light on this.

8

does the issue exist in safe mode? typically these errors we have seen are caused by the HA frontend directly or a custom card

1 Like