v 1.2.0Beta

[moddroid94]

v1.2.0Beta - Prerelease

Spotify-Breaking Change:

After the big Rip accomplished by anna's blog, Spotify has partially reworked/blocked most of the free calls we were using before, because of this it is now strongly suggested to use the new OAuth credentials Obtained from Spotify Developers Dashboard, and set them accordingly in the settings of the app.

This new method comes with a slight risk increase, as we now use credentials directly linked to the spotify account, therefore it is even MORE strongly suggested to create a disposable account to use this app, to avoid the ban of your main account.

We're a not responsible for your account getting banned, you may loose everything related to it, BE MINDFUL

Recap:

This version implements a complete refactor of the Metadata API calls logic.
Adds the option to use Developers OAuth credentials from Spotify, fixes a lot of with failed calls and failing downloads, and adds some QoL improvements like a popup when a song or playlist is unavailable.

Thanks to @respondcreate for the contributions!

Tests reports are welcome on the Discussion linked, and of course as Issue if necessary.

Happy Listening and Happy New Year!

What's Changed

• Fix: Address Spotify API Rate Limiting Issues by @respondcreate in Fix: Address Spotify API Rate Limiting Issues #276

New Contributors

• @respondcreate made their first contribution in Fix: Address Spotify API Rate Limiting Issues #276

Full Changelog: v1.1.4...v1.1.5beta

---

This discussion was created from the release v 1.2.0Beta.

[Wareuser]

weird, when i launch the windows x64.exe it still states V1.1.4...

[moddroid94]

yeah i forgot to bump the version in the source 😅

[SoleLevel]

Thanks for all your work on fixing the 429 errors! I can confirm that using my personal client ID and secret now works for me. Just FYI at the moment it seems like Spotify has disabled creating new applications in the developer portal. Most likely this is because of the Anna's Archive business. So it's currently not possible to use a dummy account to create an application unless you already happen to have one.

[moddroid94]

thanks for the confirmation! we are aware of that, we're gonna wait to see what they're going to do with them, if it breaks, which is likely, we will see how to go forward depending on the case.

Cheers

[Ominus404]

Thanks, this does work with your own client id and secret, but now i can see just how many api calls the app makes when i download songs and am wondering if there is any way to prevent needless api calls?

For instance, my main playlist is about to reach 1000 songs, i used this version to update it, it does detect that i already have 99% of the songs downloaded but it still makes an api call to /v1/tracks for each track it checks, which got me close to 600 api checks before i closed the app as i only needed to download the 12 new songs i added to my fav list.

Could we perhaps download the playlist then compare that to all the songs we already have downloaded in the folder we set and then only make an api call for tracks we don't yet have downloaded?

I'm using an app called spotify playlist to M3U that only downloads the playlist then searches a selected folder for those songs to make me a local playlist, it only makes a single api call for the playlist and then checks all the songs locally.

I guess for now the easiest way to avoid this would be for me making a seperate playlist with only the songs i need to download, that would avoid too many unnecessary api calls.

Thanks again for updating onthespot and getting it working again :)

[respondcreate]

Thanks, this does work with your own client id and secret, but now i can see just how many api calls the app makes when i download songs and am wondering if there is any way to prevent needless api calls?

For instance, my main playlist is about to reach 1000 songs, i used this version to update it, it does detect that i already have 99% of the songs downloaded but it still makes an api call to /v1/tracks for each track it checks, which got me close to 600 api checks before i closed the app as i only needed to download the 12 new songs i added to my fav list.

Could we perhaps download the playlist then compare that to all the songs we already have downloaded in the folder we set and then only make an api call for tracks we don't yet have downloaded?

I'm using an app called spotify playlist to M3U that only downloads the playlist then searches a selected folder for those songs to make me a local playlist, it only makes a single api call for the playlist and then checks all the songs locally.

I guess for now the easiest way to avoid this would be for me making a seperate playlist with only the songs i need to download, that would avoid too many unnecessary api calls.

Thanks again for updating onthespot and getting it working again :)

Hey @Ominus404 ! Thanks for the kind words and for flagging this...being mindful of API usage is important, and I appreciate you keeping an eye on it!

What you're experiencing is actually a one-time cache invalidation rather than an ongoing increase in API calls. Here's a quick primer on how things work under-the-hood: OnTheSpot caches API responses to avoid redundant network requests. It does this by generating a "checksum" (a unique fingerprint) based on the exact URL being requested from Spotify's Web API, including all query parameters. When the app needs data, it checks if a cached response exists for that URL's checksum...if one is found, it uses the cache ("cache hit") instead of calling Spotify's API.

The change in this release switches from librespot-generated tokens to OAuth client credentials for Spotify Web API calls. The old approach included a query parameter called market=from_token in every request, but OAuth authentication returns HTTP 400 errors with that parameter, so it had to be removed. This means the URLs are now slightly different, which produces different checksums, which means your existing cache no longer matches, resulting in cache "misses" and fresh API calls.

The good news is that I tested this myself and can confirm it's truly one-time. Once your playlist's tracks are fetched with the new URL format, they're cached under the new checksums, and subsequent syncs will hit the cache as expected. So your 1000-song playlist will cause extra API calls this first time, but future updates should only need calls for genuinely new tracks.

I hope this information helps! Don't hesitate to ask any follow-up questions, happy to answer what I can.

[Ominus404]

Thank you for such a detailed explanation! There were barely any api calls yesterday when i downloaded another 20 songs to update my fav list. i feel less worried now that i might get banned, and if i do, i'll already have my playlists of favorite songs saved locally 😃 .

Thanks again for working on this awesome app!

[Fares-Basousy]

Are the OAuth credentials required even for premium accounts and i still keep getting the 429 error even for single track download (checked off all the optional metadata options
and thanks for working on this project as its my main source of offline music (i have a prem account and this is better)
incredible work!

[Ominus404]

Yes, it would not work for me unless i used my own credentials. i also had to create a temporary playlist for my liked songs as it wouldn't pull the songs from there like it used to before the api changes in spotify.