Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Older IOS devices "Custom element doesn’t exist" #257

Open
dwhall96 opened this issue Dec 23, 2023 · 11 comments
Open

Older IOS devices "Custom element doesn’t exist" #257

dwhall96 opened this issue Dec 23, 2023 · 11 comments

Comments

@dwhall96
Copy link

dwhall96 commented Dec 23, 2023

Issue exists only on older IOS devices in my testing Card does not load with error "Custom Element doesn't exist", issue is not present on newer devices.

I have tested 3 different IOS IPAD Air A1475 version 12.5.7 with the same results. I have cleared cache, deleted and reinstalled the IOS app and tested Chrome browser with the same results. I also installed an older version of the bubble card.

These devices may be too old to consider supported but wanted to raise a issue in case it is a feasible fix.

@Clooos
Copy link
Owner

Clooos commented Dec 26, 2023

Hi and thank you for that interesting feedback!

Could you try to add this to your config?

frontend:
  extra_module_url:
    - /hacsfiles/Bubble-Card/bubble-pop-up.js?v=0.0.0
  extra_js_url_es5:
    - /hacsfiles/Bubble-Card/bubble-pop-up.js?v=0.0.0

Just replace 0.0.0 with your actual version.

Edit: Is this only happening with the bubble-pop-up.js module or with all Bubble Card?

@dwhall96
Copy link
Author

image
I added the lines to the config as requested but the issue persists.
to note I did restart HA, cleared cache and even tested multiple devices app and browser to confirm.

This is happening with all bubble cards. I have setup only a few pop ups, separators and buttons for a test run, each have the Custom element doesn't exist errors on the older devices but work great on newer devices that I love (which is why I am reaching out).

I want to add that the bubble card is not the only custom cards that are having the same issue on these old devices. While it is not all of the custom cards from HACS there are some that display the same error so this could be common and it is feasible it is on my side. As an example mushroom cards work fine as well as some slider cards and TV control but the issue is the same for a clock-weather-card I use. Googling this error takes me down a few paths so still on the testing phase to see if its fixable. Any help is appreciated but I understand if this is not something you can assist with.

@ModestoHagney
Copy link

Did you ever have any luck with this? I'm having the same issue on an old iPad mini I have as a wall mounted tablet.

@dwhall96
Copy link
Author

No luck, I found that the old iPad architecture does not play nice with anything HA. There is a chance you can get it to a stable state but one update or change can cause more issues than it’s worth. Its sucks because I have a stack of old iPads that could use but I was forced to resort to cheaper android tabs.

@ModestoHagney
Copy link

Darn, guess I’ll just go back to mushroom cards on the iPad for now.

@Clooos
Copy link
Owner

Clooos commented Feb 25, 2024

This is true for now, but I still hope to be able to makes it working on older devices.

@ModestoHagney
Copy link

Let me know if there’s any logs or info you need.

@Clooos
Copy link
Owner

Clooos commented Feb 26, 2024

It would be great, in your Home Assistant logs you should have some errors when Bubble Card is loaded on you view.

@ModestoHagney
Copy link

Sorry it's taken so long. I finally got around to actually looking into this. I loaded up the Dashboard I use on my phone on the iPad and had a look through the logs, I can't seem to fins anything relevant anywhere. What logs should I be looking looking at?

@Clooos
Copy link
Owner

Clooos commented Jun 17, 2024

Have you taken a look at the Home Assistant logs in Settings > System > Logs?

@ModestoHagney
Copy link

That’s where I was looking, I had the logs open while I loaded the dashboard. Reloaded the logs, went through a bunch of the different logs, couldn’t see anything relevant. I’ll try clearing the logs and looking again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants