kellnerd: harmony is having an interesting time rn with a release from spotify, where i have the link open to the release in another tab but harmony shows an error saying resource not found with the api.spotify.com link
YoMo12[m] uploaded an image: (129KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/YrTACrsGnOlRJSmHGEbLLgWT/Screenshot_20251021_112435_Spotify.jpg >
2025-10-21 29401, 2025
YoMo12[m]
This is what I see in Spotify
2025-10-21 29400, 2025
kellnerd[m]
Interesting, so this is both a regional thing and a pre-release issue 👀
2025-10-21 29445, 2025
kellnerd[m]
I have no example for this so far and the [linked ticket](https://github.com/kellnerd/harmony/issue… might be a different issue, so we should probably create a new one (unless this starts working within 24 hours).
2025-10-21 29422, 2025
julian45[m]
it might start working in 24 hrs, as it released in japan ~30 mins ago and has yet to propagate to other regions
2025-10-21 29431, 2025
julian45[m]
but worth keeping an eye on
2025-10-21 29430, 2025
julian45[m]
<kellnerd[m]> "There was [a related API..." <- both release direct lookup and barcode identification i guess? i put the release url (as viewed from a japanese IP fwiw) straight from another tab into harmony and got the error
2025-10-21 29402, 2025
julian45[m]
so theoretically it knew the release id to look up in spotify's API but spotify gave it an unhandle-able response?
2025-10-21 29403, 2025
julian45[m]
though i also experimented with pulling the release's barcode off apple music and solely searching that instead with region jp in harmony; harmony got the release from apple music but didn't report back/link to the spotify release
2025-10-21 29424, 2025
kellnerd[m]
<julian45[m]> "so theoretically it knew the..." <- The API returns exactly the error response which Harmony displays. So there is no way to distinguish this from a regular 404 response (i.e. for a made-up release ID).
2025-10-21 29430, 2025
julian45[m]
i'm starting to think this error might be related to the presence of a prerelease? normal releases from other artist under the above artist's label family (one of the many labels under sony music's japan arm) are resolving just fine as of now
2025-10-21 29446, 2025
julian45[m]
link to come in a sec
2025-10-21 29452, 2025
julian45[m]
(if desired)
2025-10-21 29448, 2025
julian45[m]
yeah, [this](https://harmony.pulsewidth.org.uk/release?spotify=38oQp2QjYNPGpXu6yu5B73>in=4547366783384&itunes=®ion=JP&ts=1761061645) came through fine - and it's not just another sony label like Ling tosite sigure's above (sony music associate records), it's an imprint *of* that label, so i think i can rule out differing label practices as a confounding factor here
2025-10-21 29438, 2025
kellnerd[m]
Interesting, the pre-release seems to be the main issue indeed. Your second example isn't available in Europe (yet), but it still works. The currently available regions are east of the "release meridian".
