429 Error
Always Prompting 429 Error
Section titled “Always Prompting 429 Error”Always prompts a 429 error when performing operations.
Spotify returned 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 Tutorial.
Or wait until Spotify stops returning 429 errors.
Extended 429 Error
Section titled “Extended 429 Error”After configuring a custom API Client and using it for a while, a 429 error appears indicating a wait time of several thousand or tens of thousands of seconds.
Continuous usage for too long. Using it for over ten hours continuously, or using Lyricify for several hours without playing songs, increases the chance of encountering an extended 429 error.
Solution
Section titled “Solution”- Create a new Client, then log in and authorize again in Lyricify.
- You can also wait until the 429 error ends.
Some Suggestions
Section titled “Some Suggestions”- Try to avoid continuous usage for extended periods (over 10 hours), as this can lead to exceeding the request threshold of the Spotify API, significantly increasing the likelihood 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 for several hours (at least 1-3 hours) in this case will lead to a 429 error. (On Android devices, please close the background when not using Lyricify; if not closed, it will continuously send requests, causing an extended 429 error. On iOS devices and some Android devices, it can remain in the background without closing.)