[BUG]: Spotify returning 429

[CustomTag]

NodeLink version

v3.4.0

Description

this error happens with the latest spotify update they did returning fake 429
There should be a bypass for that idk what tho

Client

Lavalink-Client (https://github.com/Tomato6966/lavalink-client)

Steps to reproduce

Playing tracks from spotify

Example code

No response

Confirmations

• My environment meets the minimum requirements.
• I have verified that this is not a duplicate issue.

Code of Conduct

• I agree to follow this project's Code of Conduct

[1Lucas1apk]

Hi, thanks for reporting. To be honest, I don't know how to get around this. I was investigating, and now I can no longer use the Spotify API because of error 429 (apparently a real one) that won't disappear after hours (all endpoints). Well, I'll use a VPN in the meantime. I just wanted to ask if you have any valid information to help us. If not, that's okay, but I believe we'll be able to work around this problem soon :)

[1Lucas1apk]

Hello again, I ask that you test the version on the dev branch (git checkout dev); basically, the "fake 429" error only occurs with external APIs using internal access tokens, for example, it returns the same error as https://github.com/topi314/spotify-tokener. The official Spotify OAuth is definitely reaching its request limit, so a timeout from Spotify itself has been added to the requests. This can sometimes cause slowdowns with high traffic, but I've also added the possibility of using external tokens using the same logic, but instead of an external API, I used an internal one. You can search and resolve this with tracks, playlists, and albums, but unfortunately, the ISRC doesn't work in this case. If it works, let me know.

[CustomTag]

Hello again, I ask that you test the version on the dev branch (git checkout dev); basically, the "fake 429" error only occurs with external APIs using internal access tokens, for example, it returns the same error as https://github.com/topi314/spotify-tokener. The official Spotify OAuth is definitely reaching its request limit, so a timeout from Spotify itself has been added to the requests. This can sometimes cause slowdowns with high traffic, but I've also added the possibility of using external tokens using the same logic, but instead of an external API, I used an internal one. You can search and resolve this with tracks, playlists, and albums, but unfortunately, the ISRC doesn't work in this case. If it works, let me know.

Hey Lucas there is a away to get pass this by using the spotify partner api, as thats the only away to get it to work again.
I will try to use the dev branch and get back to you if it works!

[1Lucas1apk]

This was implemented 40f1928 I spent hours reverse engineering to arrive at this solution.

[CustomTag]

This was implemented 40f1928 I spent hours reverse engineering to arrive at this solution.

Okay I will test the this solution with the dev branch and see if that helps!

[1Lucas1apk]

Hi, I wanted to know if this problem has been resolved so I can close this issue