ERROR 429 (Too many request) #31
Comments
Which redirect URIs need to be registered with spotify so I don't get a "INVALID_CLIENT: Invalid redirect URI" error? |
@LittleStinky123 did you manually change the clientID and recompiled the project or did you expose it in a settings file as well? |
@pizzadudez I only did the changes I mentioned in #37 (comment) . I had to recompile it with my changes, the most time consuming part was setting up a spotify developer account anyway. |
@LittleStinky123 I didn't see your comment on #37 before writing. I was wondering mostly if someone has already moved the spotify client credentials in a settings file to make the process easier for everyone using this app. I don't currently have the setup to recompile it but I'll get the necessary dependecies and look into maybe adding this feature I mentioned. |
Just wondering if you ever did do a tutorial - trying to follow the comments but I they're spread out over diff issues and I'm not the most apt regardless |
Hello mates,
I want to post this issue because recently a lot of EZBlocker's users have received this annoying error.
Here directly from Spotify documentation
For all users that are using EZBlocker 2 this is a really bad news because to check Spotify status, EZBlocker makes a request every 500ms to the Web API...
This means that EZBlocker couldn't detect current playing song (and so if you are playing ads) correctly
To solve this
issue
I'll make a guide on how to create a personal EZBlocker with custom Client ID.Thanks for your attention :)
The text was updated successfully, but these errors were encountered: