429 Error
Always Prompting 429 Error
Section titled “Always Prompting 429 Error”Always prompts a 429 error when performing operations.
Spotify returns a 429 Too Many Requests error, which is not Lyricify’s fault.
Solution
Section titled “Solution”Configure a custom API Client, refer to the Custom Spotify API Client Configuration Guide.
If you don’t want to configure it, you can choose to wait until Spotify stops returning 429 errors.
If it’s a song request operation, it’s recommended to perform it in the Spotify client.
Extended 429 Error
Section titled “Extended 429 Error”After configuring a custom API Client and using it for a while, it prompts a 429 error with a wait time of several thousand or tens of thousands of seconds.
Continuous usage for too long. Using for several hours continuously, or using Lyricify for several hours without playing songs, increases the chance of encountering an extended 429 error.
Solution
Section titled “Solution”- After configuring a custom API Client, authorize the public API client as prompted. This way, when encountering an extended 429 error, Lyricify will continue to work through the public API client. You can restart Lyricify after the wait ends to switch back to the custom API Client.
- You can also create a new Client and log in and authorize again in Lyricify.
Some Suggestions
Section titled “Some Suggestions”- Try to avoid continuous usage for too long (over 10 hours), as this can cause the request volume within a unit of time to exceed the Spotify API threshold, significantly increasing the probability of encountering an extended 429 error.
- If you use Lyricify on multiple devices with high frequency, consider creating a separate Client for each device to distribute requests and prevent triggering threshold limits.
- When not playing songs, please close Lyricify. Keeping Lyricify running in this case for several hours (at least 1-3 hours) will lead to a 429 error.