WebRTC icon indicating copy to clipboard operation
WebRTC copied to clipboard

Custom Element does not exist after 2.0.2 on old ipad.

Open 7michaelg7 opened this issue 3 years ago • 11 comments

A couple weeks ago I started getting the "Custom element doesn't exist: webrtc-camera" error on my iPad air 2 running iOS 12.5.4. The most updated version works perfectly everywhere except the iPad. I have reverted to the 2.0.2 version of the integration and everything works fine.

This thread seems to suggest it might be an issue with external resources: https://community.home-assistant.io/t/stuck-on-custom-element-doesnt-exist-need-help/73220/43

Thanks!

7michaelg7 avatar Jul 13 '21 02:07 7michaelg7

Am having the same issue on an iPad Mini 2 (well, several actually) running 12.5.4

Tried rolling back to v2.0.2 but this didn't fix things for me.

milkplus27 avatar Jul 13 '21 09:07 milkplus27

This is also happening to me on iOS devices since the update (my main driver is iPhone 6 on iOS 12.5.4; have some newer with iOS 14, need to check them). I have attempted to reset the frontend cache in the app, as well as reinstalling the app entirely and wiping all Safari data. I've tried re-installing webrtc-camera (but NOT downgrading). HomeAssistant has been restarted several times, including for core version upgrades and also the entire host. There is a reverse proxy being used on another machine that has also been restarted, and is not configured to cache in any way.

The logs are full of entries like this: 2021-07-13 10:21:17 ERROR (MainThread) [frontend.js.latest.202107070] https://<my.homeassistant.instance>/webrtc/webrtc-camera.js?v2.0.2:88:0 InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable

So it looks like, for some reason, iOS is caching that version number? Not sure why I can't reload Lovelace and fix this...

fouram avatar Jul 13 '21 15:07 fouram

Having this issue as well , but i am using a iPad Pro. It works on my android phone and all pcs just fine , but on the ipad (tried safari , edge and chrome) and the home assistant app i get the customer element does not exist.

downgrading to 2.0.2 and resetting the frontend cache in the home assistant debug menu fixed this.

stripeyhorse avatar Jul 24 '21 02:07 stripeyhorse

hello! has there been any movement on this by any chance? Being unable to update past 2.0.2 means that this component is using up a lot of background data for me which was fixed in 2.1.0

milkplus27 avatar Aug 26 '21 13:08 milkplus27

This issue maybe fixed in latest master version

AlexxIT avatar Aug 29 '21 04:08 AlexxIT

This issue maybe fixed in latest master version

hi. you mean on 2.1.1?

milkplus27 avatar Aug 29 '21 05:08 milkplus27

No, the master version does not have a number

AlexxIT avatar Aug 31 '21 15:08 AlexxIT

No, the master version does not have a number

Ah ok. So how do I update to the master version from HACS?

milkplus27 avatar Aug 31 '21 15:08 milkplus27

Oh, my bad. I found it in the drop-down. Trying now. Thanks for the heads up

milkplus27 avatar Aug 31 '21 16:08 milkplus27

Oh, my bad. I found it in the drop-down. Trying now. Thanks for the heads up

Would you mind telling me where you found this dropdown? I would like to try as well.

Edit: found it! Just like you would change the version, one of them is called 'Master'. This seems to be working for me now on my iPad but I will wait for others to report back before closing the thread.

7michaelg7 avatar Aug 31 '21 18:08 7michaelg7

So far so good for me. Thanks @AlexxIT for looking into this.

milkplus27 avatar Aug 31 '21 20:08 milkplus27

Fixed long time ago

AlexxIT avatar Jan 02 '23 13:01 AlexxIT