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 · 22 comments
Open

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

dwhall96 opened this issue Dec 23, 2023 · 22 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.

Clooos added a commit that referenced this issue Aug 16, 2024
- [x] Attempt to fix the `Custom element doesn't exist` error on Google Nest Hub. #345 and maybe #257
- [x] The pop-ups and the backdrop should be now fully reliable (finally!), and probably faster too (I’ve said that too many times). #703
- [x] An opened pop-up with a trigger entity now persist after a refresh of the dashboard. #270
- [x] It was impossible to open a pop-up with a trigger entity by using the notify action, this is now fixed! #270 #422
- [x] The slider button now supports climate entity temperature step. #715
- [x] Multiple popups auto-close bug #685
Clooos added a commit that referenced this issue Aug 21, 2024
- [x] Pop-ups are (finally) changing color accordingly when a theme change (e.g. from dark to light). #627
- [x] Vertical stack titles are now hidden if set for a pop-up. #647
- [x] Heavy pop-ups are now closing faster on some setups.
- [x] Pop-up transitions are now smoother and more reliable on some setups.
- [x] Pop-up backdrop transitions are now smoother on some setups (if not disable it, this feature can slowdown transitions).
- [x] Pop-up auto-close timeout is now removing the hash from the URL correctly.
- [x] Added the missing haptic feedback on the pop-up close button.
- [x] Some haptic feedback were fired multiple times, this should be fixed.
- [x] Finally fixed the `Custom element doesn't exist` error on Google Nest Hub! #345 and maybe #257
@Clooos
Copy link
Owner

Clooos commented Aug 21, 2024

Hi @dwhall96 and @ModestoHagney, I've released a new version that might fix this issue on older devices, can anyone confirm this?

https://github.com/Clooos/Bubble-Card/releases/tag/v2.2.3

@ModestoHagney
Copy link

Unfortunately this didn’t fix it for me, though I just went to the dashboard I use on my iphone and tried it on the iPad.

When I get home from work I’ll try making a new dashboard with just one card and see what happens.

I’ve attached a screenshot so you can see the error.

IMG_F1C79E63FDA1-1

@Clooos
Copy link
Owner

Clooos commented Aug 21, 2024

Can you provide any logs related to the frontend in the HA logs, you should see one about bubble-card.js.

@ModestoHagney
Copy link

Last time I looked through the logs I couldn’t see any related to bubble card. I was probably looking in the wrong place, I’ll take another look tonight when I get home.

@Clooos
Copy link
Owner

Clooos commented Aug 22, 2024

None of them is directly mentioning Bubble Card, it's in frontend.js or something like that.

@ModestoHagney
Copy link

2024-08-22 18:52:54.465 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/frontend", "/config/custom_components/hacs/hacs_frontend", False)]); This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 54: hass.http.register_static_path(f"{URL_BASE}/frontend", locate_dir(), cache_headers=False), please create a bug report at https://github.com/hacs/integration/issues 2024-08-22 18:52:54.475 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' calls hass.http.register_static_path which is deprecated because it does blocking I/O in the event loop, instead call await hass.http.async_register_static_paths([StaticPathConfig("/hacsfiles/iconset.js", "/config/custom_components/hacs/iconset.js", True)]); This function will be removed in 2025.7 at custom_components/hacs/frontend.py, line 57: hass.http.register_static_path(, please create a bug report at https://github.com/hacs/integration/issues 2024-08-22 18:52:54.485 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues

This is the only thing I can find that has anything to do with frontend in the logs. Unless I'm looking in the wrong logs?

@Clooos
Copy link
Owner

Clooos commented Aug 22, 2024

Nothing related to Bubble Card, but there should be some logs that mention it somewhere.

@hhu94
Copy link

hhu94 commented Aug 30, 2024

I'm seeing the exact same behavior as @ModestoHagney. I wonder if this is somehow related to home-assistant/frontend#21004, which was fixed in the HA frontend two months ago.

@Clooos
Copy link
Owner

Clooos commented Aug 30, 2024

I have no idea, but even if I find a way to make it works on older devices, most of the CSS styles are too modern, and making it "visually compatible" would probably be a nightmare for me 😅

To be honest this issue is likely the one with the lowest priority for me right now.

But if anyone can provide me any logs, from the browser console or from Home Assistant, I will try to makes it compatible, the CSS styles would be the next step.

@ModestoHagney
Copy link

I'm away from home at the moment so I can only grab logs from HA remotely at the moment sorry, but I doubt there will be anything relevant as it's not being used. If you let me know what logs you need, I can grab some while I'm back there in the weekend. I had a brief look through last time, but I couldn't find anything relevant. I assume I'm just not looking in the right place.

@dougrathbone
Copy link

I'm reporting this pretty broadly across devices. IPad 4, 2N Intercom (Android), and iPhone 10.

These arent brand new devices, but they also arent that out of date from an OS updates POV. The 2N device especially is quite new.

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

5 participants