mirror of
https://github.com/alexk218/tagify.git
synced 2026-04-27 04:15:49 +03:00
[GH-ISSUE #31] Intermittent track metadata loading failure after recent update #5
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tagify#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @My-name-is-user on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/alexk218/tagify/issues/31
Hi Alex,
First off, thank you for building and maintaining Tagify — it's an incredibly useful tool for organizing my Spotify library!
I've encountered an issue after the latest update. Track metadata (such as BPM, release date, lenght, etc.) started loading again initially, but it behaves very inconsistently/episodically:
For the first ~2 minutes after opening Spotify everything works fine — track info loads normally.
Then, without any visible errors in UI, metadata suddenly stops loading for tracks with tagging(except rating and energy level).
Additionally, navigation between albums and artists becomes unresponsive — clicking on sections or links doesn't load the content.
When clicking on built-in Spotify links in the interface (e.g., artist name or track title), Spotify shows its internal error message: "Couldn't load the info" (or similar — the standard Spotify message about being unable to load information).
Restarting Spotify or waiting some time can temporarily fixes it for another couple of minutes, but the problem returns.
I'm on the latest version of Tagify (installed via your the official .exe script), Spicetify, and the Spotify desktop app [2.2.0, 2.42.7, 1.2.79, win].
Let me know if you need any logs, console output, or more details to reproduce this.
@alexk218 commented on GitHub (Jan 9, 2026):
Do these errors (like "Couldn't load the info") only appear when interacting with items WITHIN Tagify - like the artist name/title within the Tagify interface. Or does this also happen outside of Tagify?
I see that you have 4000+ tagged tracks... another user with many tagged tracks mentioned they were having issues: https://github.com/alexk218/tagify/discussions/25
Can you take a look at the latest messages from yesterday and tell me if you're having the same problem?
After updating Tagify to the latest version, Tagify begins making requests to Spotify for every single one of your tagged tracks, and caching your tag data (storing it locally for future use). It's possible that this is causing problems for users with many tagged tracks, since it will take some time for Tagify to make all the necessary requests - and will behave weirdly until this is completed.
Also, please open up DevTools and send me the error messages that you receive. This will help me determine what the problem is.
Thanks for the detailed write up! I'll be working hard this weekend to make sure all problems are resolved.
@My-name-is-user commented on GitHub (Jan 10, 2026):
Thanks for the quick responses and for planning to work on this over the weekend!
About where the errors appear
The "Couldn't load the info" errors and the broken navigation (clicking artist name or track title) happen regardless of whether I trigger the navigation inside the Tagify interface or directly in the main Spotify UI. As soon as Tagify stops receiving metadata from Spotify, navigation stops working everywhere.
Comparison with issue #25
I looked at the latest comments in #25. My symptoms are different — my filters continue to work perfectly in both states (when metadata is loading normally and when it stops loading completely). Just to be sure, I also cleared the cache and let it fully rebuild, but the metadata loading issue still occurs periodically.
DevTools log
I’ve attached a console log from a session where the problem occurred (file: xpui.app.spotify.com-1768006134712.log).
In the Network tab I see a large number of Spotify API requests returning 429 Too Many Requests. It looks like Spotify is temporarily rate-limiting the client because of too many rapid requests. As soon as the 429 responses stop appearing, metadata starts loading again and navigation works normally until the next wave of rate-limiting hits.
Let me know if you need more details or another type of log! Thanks again for the help!
xpui.app.spotify.com-1768006134712.log
@alexk218 commented on GitHub (Jan 11, 2026):
Hey! I've been working on this all weekend, made some progress.
Can you reach out to me on Discord? https://discord.gg/C4qbPUbBKV
I have some questions for you - so I can reproduce this better.
@My-name-is-user commented on GitHub (Mar 8, 2026):
Hi again Alex,
I wanted to let you know that I’ve resolved the issue by installing the latest beta version from your Discord server. It’s working great now.
Thank you for the update and for all the amazing work you’re doing on this project!
@alexk218 commented on GitHub (Mar 8, 2026):
Happy to hear :)