[GH-ISSUE #941] Large 'liked tracks' does not laod #1500

Open
opened 2026-03-14 15:16:51 +03:00 by kerem · 3 comments
Owner

Originally created by @domgregori on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/941

Describe the bug
When going to LikedTrackPage with a large library (10,000), it does not load. Stays at Loading...

To Reproduce
gy, go to LikedTrackPage

Expected behaviour
Load my liked tracks

Log and backtrace

2026-02-27T05:03:11.117863Z  INFO client_request{request=GetCurrentUserQueue}: spotify_player::client: Successfully handled the client request, took: 680ms
2026-02-27T05:03:13.671893Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/following?type=artist&limit=20&after=0CjWKoS55T7DOt0HJuwF1H: {
  "error": {
    "status": 429,
    "message": "API rate limit exceeded"
  }
}
2026-02-27T05:03:13.689197Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/tracks: {
  "error": {
    "status": 429,
    "message": "API rate limit exceeded"
  }
}
2026-02-27T05:03:13.726114Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests
2026-02-27T05:03:13.821360Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/tracks: {
  "error": {
    "status": 429,
    "message": "API rate limit exceeded"
  }
}
2026-02-27T05:03:13.830629Z  INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Tracks(TracksId { uri: "tracks:user-liked-tracks", kind: "Liked Tracks" }))), update the context state
2026-02-27T05:03:14.689306Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests

Backtrace empty

Environment

  • OS: 6.12.63-1-MANJARO
  • Application version: 0.22.1
  • Application features:
Compile-time features:
  ✗ daemon
  ✓ streaming
  ✓ media-control
  ✓ image
  ✓ viuer
  ✗ sixel
  ✗ pixelate
  ✓ notify
  ✗ fzf
  ✗ pulseaudio-backend
  ✗ alsa-backend
  ✓ rodio-backend
  ✗ jackaudio-backend
  ✗ sdl-backend
  ✗ gstreamer-backend
Originally created by @domgregori on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/aome510/spotify-player/issues/941 **Describe the bug** When going to LikedTrackPage with a large library (10,000), it does not load. Stays at Loading... **To Reproduce** gy, go to LikedTrackPage **Expected behaviour** Load my liked tracks **Log and backtrace** ``` 2026-02-27T05:03:11.117863Z INFO client_request{request=GetCurrentUserQueue}: spotify_player::client: Successfully handled the client request, took: 680ms 2026-02-27T05:03:13.671893Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/following?type=artist&limit=20&after=0CjWKoS55T7DOt0HJuwF1H: { "error": { "status": 429, "message": "API rate limit exceeded" } } 2026-02-27T05:03:13.689197Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/tracks: { "error": { "status": 429, "message": "API rate limit exceeded" } } 2026-02-27T05:03:13.726114Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests 2026-02-27T05:03:13.821360Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/tracks: { "error": { "status": 429, "message": "API rate limit exceeded" } } 2026-02-27T05:03:13.830629Z INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Tracks(TracksId { uri: "tracks:user-liked-tracks", kind: "Liked Tracks" }))), update the context state 2026-02-27T05:03:14.689306Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests ``` Backtrace empty **Environment** - OS: 6.12.63-1-MANJARO - Application version: 0.22.1 - Application features: ``` Compile-time features: ✗ daemon ✓ streaming ✓ media-control ✓ image ✓ viuer ✗ sixel ✗ pixelate ✓ notify ✗ fzf ✗ pulseaudio-backend ✗ alsa-backend ✓ rodio-backend ✗ jackaudio-backend ✗ sdl-backend ✗ gstreamer-backend ```
Author
Owner

@Knightsmarian commented on GitHub (Mar 2, 2026):

I put a new pr out last night to address the new api endpoints and raté limits for error code 429

<!-- gh-comment-id:3985384944 --> @Knightsmarian commented on GitHub (Mar 2, 2026): I put a new pr out last night to address the new api endpoints and raté limits for error code 429
Author
Owner

@domgregori commented on GitHub (Mar 4, 2026):

I built with the 942 pr (commit bfd0a6f0d9) but still getting the 429 error.

2026-03-04T15:57:08.969332Z  INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Tracks(TracksId { uri: "tracks:user-liked-tracks", kind: "Liked Tracks" }))), update the context state
2026-03-04T15:57:11.151728Z ERROR client_request{request=GetContext(Tracks(TracksId { uri: "tracks:user-liked-tracks", kind: "Liked Tracks" }))}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/tracks: {
  "error": {
    "status": 429,
    "message": "API rate limit exceeded"
  }
}
<!-- gh-comment-id:3998585002 --> @domgregori commented on GitHub (Mar 4, 2026): I built with the 942 pr (commit bfd0a6f0d906d85bb6c7955fb3b42d06ce2d0ef6) but still getting the 429 error. ``` 2026-03-04T15:57:08.969332Z INFO spotify_player::client::handlers: Current context ID (None) is different from the expected ID (Some(Tracks(TracksId { uri: "tracks:user-liked-tracks", kind: "Liked Tracks" }))), update the context state 2026-03-04T15:57:11.151728Z ERROR client_request{request=GetContext(Tracks(TracksId { uri: "tracks:user-liked-tracks", kind: "Liked Tracks" }))}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/tracks: { "error": { "status": 429, "message": "API rate limit exceeded" } } ```
Author
Owner

@aome510 commented on GitHub (Mar 4, 2026):

it's possible that parallel settings in github.com/aome510/spotify-player@6cdcb784da/spotify_player/src/client/mod.rs (L1508) cause the rate-limit issue. My liked track is not that big so I haven't never encountered any issue. You can play around with the settings or add delays between requests to see if it fixes 429 issues

regarding new API endpoint, I didn't see any issue with my spotify_player app, so not sure what went wrong

<!-- gh-comment-id:3998846105 --> @aome510 commented on GitHub (Mar 4, 2026): it's possible that parallel settings in https://github.com/aome510/spotify-player/blob/6cdcb784dace48f4e6fc8834d1515e3401352239/spotify_player/src/client/mod.rs#L1508 cause the rate-limit issue. My liked track is not that big so I haven't never encountered any issue. You can play around with the settings or add delays between requests to see if it fixes 429 issues regarding new API endpoint, I didn't see any issue with my `spotify_player` app, so not sure what went wrong
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-player#1500
No description provided.