Wrong track count for Apple music

[fabi321]

For some reason, Harmony reports that there is one track less than all other platforms. But I see the correct track count both in web as well as using the Apple Music API.
I am honestly lost as to why that is.
https://harmony.pulsewidth.org.uk/release/actions?release_mbid=7b0baf97-022c-4636-83a7-ce1cfd1189c3

[kellnerd]

I am honestly lost as to why that is.

Me too, for some reason the old iTunes API doesn't return track 6 for this release: https://harmony.pulsewidth.org.uk/release?itunes=1843070471&region=US&ts=1762085960

Since this issue is similar to #104, it can be "fixed" the same way.
But if you say the Apple Music API doesn't have this issue, migrating to that API would be the better long term solution, provided we have an API key for it.

[fabi321]

For an API key, see #5 (comment)

I am not sure, if Harmony is doing requests on the server side or client side. If it does them server side, that would fix the issue.

I'm not stupid enough to pay 100$/yr for an api key ;)

[kellnerd]

Thanks, that looks useful. API requests are currently performed on the server side, so that is going to help for local development at least.
I am only a bit worried about using a scraped token for a public, server-side app which causes significantly more traffic originating from the same IP address.

Earlier this year I was discussing the topic with @rphsoftware and they said that the official developer API and the inofficial API used by the Apple Music web app are similar enough to support both with one implementation.
So ideally Harmony's implementation would support both and the public server would use official credentials. I also wouldn't pay that price myself, but there have been offers to donate existing credentials to Harmony (or even pay the costs for it!) in the past.

[fabi321]

From my testing, I can use both apis (https://amp-api.music.apple.com/v1/ and https://api.music.apple.com/v1/) with this token. I am personally currently using amp-api, but more as a precaution, and the library I'm using is designed for api.

It also looks like it is intended for "the frontend", so it is supposed to get some traffic.
The thing I'm more worried about is the stability of it. So far it works, but I believe that might change once they redeploy their frontend.