Conversation
Same stale-APQ-hash pattern as getAlbum: the embedded queryArtistOverview hash no longer matches the query published in Spotify's current web-player bundle. Refreshed it via the repository's own resolve-spotify-hashes.py. No other hashes changed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sibling fix to #6 — same root cause, different operation.
While resolving the
getAlbumhash for #6, I ran the repo'sresolve-spotify-hashes.pyacross all operations and noticedqueryArtistOverviewis also stale versus Spotify's current web-player bundle:Unlike #6, I haven't actually hit an artist-page failure myself — no error log to show here — so this one is proactive: it's the same republish drift and will likely break the same way, but I can't point to a broken screen yet. Refreshed just that single hash, nothing else.
Same heads up as #6: I'm only on macOS right now, so I couldn't build/test on hardware — this is unverified. I'll validate on a real Switch once I get to a Windows machine and report back here. Totally fine to just decline it in the meantime; only opening it in case a ready-made patch is useful.
🤖 Generated with Claude Code