Environment
- sonn core: 4.0.0-beta.21
- Soloist: 1.3.8.36 build 1789106507 (20260911) (g5c3a2053ac)
- linux/x86_64
- Spotify integration
Note: Account names and Spotify usernames in the examples below have been anonymized.
Problem
Opening the Spotify playlist browser can cause sonn to request the user's playlists with limit=120.
Spotify rejects this request with HTTP 400 and reports:
As a result, the Spotify playlist browser can return no playlists.
Log
The Content Manager requests:
folderId=playlists limit=120 offset=0 service=spotify user=AccountA
The resulting Spotify API request is:
https://api.spotify.com/v1/me/playlists?offset=0&limit=120
Spotify responds with:
status=400
message="Invalid limit"
The same invalid request is reproducible.
Actual result
sonn requests the Spotify playlists endpoint using:
Spotify rejects the request with HTTP 400, so the playlist browser cannot retrieve the playlist list.
Expected result
sonn should use a page size accepted by the Spotify API and paginate the results when more playlists need to be retrieved.
Additional observation
Spotify authentication itself succeeds and the account has the required playlist-read scopes.
This therefore appears to be a playlist-browser/API pagination issue rather than an authentication failure.
This issue is separate from #379, which tracks playlist expansion failing after a second Spotify account is configured.
Environment
Problem
Opening the Spotify playlist browser can cause sonn to request the user's playlists with
limit=120.Spotify rejects this request with HTTP 400 and reports:
As a result, the Spotify playlist browser can return no playlists.
Log
The Content Manager requests:
The resulting Spotify API request is:
Spotify responds with:
The same invalid request is reproducible.
Actual result
sonn requests the Spotify playlists endpoint using:
Spotify rejects the request with HTTP 400, so the playlist browser cannot retrieve the playlist list.
Expected result
sonn should use a page size accepted by the Spotify API and paginate the results when more playlists need to be retrieved.
Additional observation
Spotify authentication itself succeeds and the account has the required playlist-read scopes.
This therefore appears to be a playlist-browser/API pagination issue rather than an authentication failure.
This issue is separate from #379, which tracks playlist expansion failing after a second Spotify account is configured.