Version 1.3.1 only shows one playlist

[moabeat-berlin]

Describe the bug
Version 1.3.1 shows only one playlist.

To Reproduce

1. Open ncspot
2. Go to the playlist section
3. Only one playlist shows up for me

Expected behavior
All playlists of my account should be shown.

Screenshots

System (please complete the following information):

• OS: Linux (Arch)
• Terminal: Konsole
• Version: 1.3.1
• Installed from: AUR (ncspot-bin, ncspot-ncurses), so the binary release and a self-built one

Additional context
I already tried deleting ~/.cache/ncspot entirely and logging in again, but this didn't fix the issue.

Thank you very much for releasing a new version using librespot 0.7.0 and thus fixing the bug so quickly! However, without the playlists not properly working, the restored functionality is somehow still limited. Maybe this is something in librespot rather than in ncspot, but I am not able to assess this.

[lorenashfield]

For me, only my non-collaborative playlists are shown. If anyone else added a song to the playlist it doesn't show up.

[hrkfdn]

Hmm, anything suspicious in the logs? I can't reproduce this, but I wonder if the switch to Login5 for the token caused this, maybe because the token scope has changed.

[moabeat-berlin]

When running ncspot with the --debug flag, I get a bunch of this:

[2025-08-25][22:36:28] [ureq::unit] [DEBUG] response 200 to GET https://api.spotify.com/v1/playlists/27DRsSd9SjSOqd
3AycdUmX/tracks?offset=400&market=from_token&limit=100
[2025-08-25][22:36:28] [ureq::pool] [DEBUG] adding stream to pool: https|api.spotify.com|443 -> Stream(SslStream { 
stream: TcpStream { addr: [2003:c0:df4e:f700:bc8:9bf7:81a0:fb5c]:43060, peer: [2600:1901:1:7c5::]:443, fd: 25 }, ss
l: Ssl { state: "SSL negotiation finished successfully", verify_result: X509VerifyResult { code: 0, error: "ok" } }
 })
[2025-08-25][22:36:28] [ncspot::spotify_api] [ERROR] unhandled api error: json parse error: data did not match any variant of untagged enum PlayableItem at line 1 column 54589
[2025-08-25][22:36:28] [ncspot::ui::pagination] [DEBUG] fetching next page at offset 400
[2025-08-25][22:36:28] [ncspot::spotify_api] [DEBUG] fetching playlist 27DRsSd9SjSOqd3AycdUmX tracks, offset: 400

I definitely have more than one playlist that is non-collaborative. I also should mention, I have at least two playlists having emojis in their title, but that was working fine in older versions before the API changes without issues.

[lorenashfield]

I'm getting the same issue in my debug logs. It seems like the program is repeatedly trying to make GET requests for the missing playlists as long as it is open.

[sodagunz]

I managed to reproduce, I can only see two playlists.

[2025-08-26][08:43:56] [ncspot::ui::pagination] [DEBUG] fetching next page at offset 200
[2025-08-26][08:43:56] [ncspot::spotify_api] [DEBUG] fetching playlist 3ZcAJLSa7T9QpqCgIG2MAV tracks, offset: 200
[2025-08-26][08:43:56] [rspotify_http::ureq] [INFO] Making request Request(GET https://api.spotify.com/v1/playlists/3ZcAJLSa7T9QpqCgIG2MAV/tracks, [authorization: Bearer BQAlv0pQlp4WU-kLl2z_2ALffoaSB35sehx2TxOng2hGp4K_5kMHo2OUDmwMlAoMqpmUdLf88991JgsDhe__JYSOvkrutcyJY6lyDJQYQn-musuYlVzS4ueWPFri0cM-PPFKkNZ5feQnP2-wT8u34zUOUbcqvlBb1GP6_VEBTmjFSdV7ThhoH3KIAaX2ulN54pKuCfZseygnFomLdDMRp4tz4abYQ97Pg42Xa431NKpWaa98SgrWq46J--pA74kvaKzRDqQh_QPDrSmxaVnvBmsPPcjW3J0lF0MXFfRTcuqqSPIoiWn_TdhN_Tw2v8sERPS6cfLUEaXsdZtuexDXBw2SOy1qz7HCCKdo31XjV6gpB_mXJUBUfebuBaLzrKUykWq48V1lgMBGrb8])
[2025-08-26][08:43:56] [ureq::pool] [DEBUG] pulling stream from pool: https|api.spotify.com|443 -> Stream(SslStream { stream: TcpStream { addr: [2a0c:5a84:b206:4500:741c:9147:cf1b:6882]:41074, peer: [2600:1901:1:7c5::]:443, fd: 19 }, ssl: Ssl { state: "SSL negotiation finished successfully", verify_result: X509VerifyResult { code: 0, error: "ok" } } })
[2025-08-26][08:43:56] [ureq::unit] [DEBUG] sending request (reused connection) GET https://api.spotify.com/v1/playlists/3ZcAJLSa7T9QpqCgIG2MAV/tracks?offset=200&market=from_token&limit=100
[2025-08-26][08:43:56] [ureq::unit] [DEBUG] writing prelude: GET /v1/playlists/3ZcAJLSa7T9QpqCgIG2MAV/tracks?offset=200&market=from_token&limit=100 HTTP/1.1
Host: api.spotify.com
User-Agent: ureq/2.12.1
Accept: */*
authorization: ***
[2025-08-26][08:43:57] [ureq::response] [DEBUG] Streaming body until content-length: 235505
[2025-08-26][08:43:57] [ureq::unit] [DEBUG] response 200 to GET https://api.spotify.com/v1/playlists/3ZcAJLSa7T9QpqCgIG2MAV/tracks?offset=200&market=from_token&limit=100
[2025-08-26][08:43:57] [ureq::pool] [DEBUG] adding stream to pool: https|api.spotify.com|443 -> Stream(SslStream { stream: TcpStream { addr: [2a0c:5a84:b206:4500:741c:9147:cf1b:6882]:41074, peer: [2600:1901:1:7c5::]:443, fd: 19 }, ssl: Ssl { state: "SSL negotiation finished successfully", verify_result: X509VerifyResult { code: 0, error: "ok" } } })
[2025-08-26][08:43:57] [ncspot::spotify_api] [ERROR] unhandled api error: json parse error: data did not match any variant of untagged enum PlayableItem at line 1 column 33128

This is the response I get from one such calls (limit changed from 100 to 2 for conciseness):

[Removed JSON to clear up the noise]

[hrkfdn]

[2025-08-26][08:43:57] [ncspot::spotify_api] [ERROR] unhandled api error: json parse error: data did not match any variant of untagged enum PlayableItem at line 1 column 33128

This seems to suggest that rspotify was unable to deserialize one of the items in the playlist. Anything special in there? Podcast episode? Local file?

[sodagunz]

You are right, something about this playlist in particular that rspotify does not like. Maybe it's that it's over 1400 tracks long and has some titles that are borderline abusive of UTF-8?

I opened a similar ticket about the same playlist back in the day, here. The symptoms now are different, but the root cause is likely to be the same.

Anyhow, sorry @moabeat-berlin for the noise, I guess I can't actually reproduce, unless we have similar playlists.
To find the offending playlist in your case, I did something like

ncspot -d debug.log
# wait for a few seconds
rg "updating playlist" debug.log

Output:

195:[2025-08-26][14:54:36] [ncspot::library] [INFO] updating playlist This Is Mercedes Sosa (index: 0)
225:[2025-08-26][14:54:37] [ncspot::library] [INFO] updating playlist Best of Fela Kuti (index: 1)
263:[2025-08-26][14:54:37] [ncspot::library] [INFO] updating playlist Disclosure's Record Bag 💼 📦 💿 (index: 2)

The third one never finishes loading, nor do the rest of my playlists. My log is >3000 lines, after line 300 it's just the playlist pagination loop of dread I posted on my previous comment.

[hrkfdn]

I think it's the same problem I already reported here: ramsayleung/rspotify#320

[hrkfdn]

Looks like there's already a fix upstream, just needs to be released: ramsayleung/rspotify#525

[sodagunz]

That's amazing news!

I'm still confused as to what could have cause the behaviour to change between 1.3.0 and 1.3.1.

• On 1.3.0, I only get into a loop of death after attempting to open the playlist, at which point ncspot crashes completely (I can't even ctrl+z nor ctrl+d). All playlists get listed correctly, as long as I don't try and play the offending one things are fine.
• On 1.3.1, I get the into the loop as soon as I open ncspot. The application does not freeze, but it fails to load any playlist after the offending one.

I'll try and take a look at it whenever I have some time 👁️ 👄 👁️

[hrkfdn]

The looping part is weird indeed, sounds like something that needs to be fixed on ncspot side.

[sodagunz]

I can confirm it's indeed failing to parse exactly on the column where a podcast episode appears instead of a track. 👍

 curl --request GET \                                                                                                                                                                                        
     --url 'https://api.spotify.com/v1/playlists/3ZcAJLSa7T9QpqCgIG2MAV/tracks?market=ES&limit=100&offset=200' \
     --header 'Authorization: Bearer your-own-token''

@ col 33128

[lorenashfield]

I removed the podcast from my playlist and the issue was fixed. Seems like the program gets caught up looping on the parse error from the podcast and can't load any further playlists.