hacs / integration

HACS gives you a powerful UI to handle downloads of all your custom needs.
https://hacs.xyz
MIT License
5.42k stars 1.29k forks source link

Removing a dashboard repo doesn't clean up .storage/lovelace_resources #4211

Open rsteckler opened 2 hours ago

rsteckler commented 2 hours ago

System Health details

System Information

version core-2024.11.1
installation_type Unknown
dev false
hassio false
docker false
user root
virtualenv false
python_version 3.12.4
os_name Linux
os_version 5.15.0-71-generic
arch x86_64
timezone America/Los_Angeles
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4958 Installed Version | 2.0.1 Stage | running Available Repositories | 1462 Downloaded Repositories | 15
AccuWeather can_reach_server | ok -- | -- remaining_requests | 30
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Dashboards dashboards | 5 -- | -- resources | 7 views | 14 mode | storage
Recorder oldest_recorder_run | November 10, 2024 at 4:04 AM -- | -- current_recorder_run | November 19, 2024 at 7:54 AM estimated_db_size | 1620.66 MiB database_engine | mysql database_version | 9.0.1
Spotify api_endpoint_reachable | ok -- | --

Checklist

Describe the issue

Removing a dashboard repo from hacs leaves the old js file referenced in the lovelace config, leading to browser console errors

Reproduction steps

  1. Add a dashboard HACS item (e.g. upcoming-media-card)
  2. Remove it from your HACS installation
  3. Note console errors showing the card javascript can't be found: image
  4. Note the entry still exists in .storage/lovelace_resources
    ./.storage/lovelace_resources:        "url": "/hacsfiles/upcoming-media-card/upcoming-media-card.js?hacstag=146783593043",

Debug logs

let me know if needed

Diagnostics dump

No response

hacs-bot[bot] commented 2 hours ago

Make sure you have read the issue guidelines and that you filled out the entire template.

If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a :+1: reaction to the issue description. Thanks! :+1: