michaelherger / Spotty-Plugin

A Spotify plugin for the Lyrion Music Server (fka. Logitech Media Server) and Squeezebox compatible players
112 stars 21 forks source link

Index of spotify fails #73

Closed NikolajHansen closed 1 year ago

NikolajHansen commented 1 year ago

Hi,

I have just upgraded to the last logitechmediaserver-8.3.0-1662405429 and upgraded the spotty helper app to spotty] spotty v1.3.1 - using librespot 0.4.2 9b95691 (Built on 2022-09-19, Build ID: 5ToCSuBf, Profile: debug)

Platform: FreeBSD squeezebox.barnabas.dk 13.1-RELEASE FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC amd64

I am having issues running the index of my music collection on spotify. The rest of the integration seems to work fine. I am able to play, browse music etc.

https://pastebin.ubuntu.com/p/nWZk7WSC5M/

Output of command:

[2022-09-20T08:14:23Z INFO spotty] spotty v1.3.1 - using librespot 0.4.2 9b95691 (Built on 2022-09-19, Build ID: 5ToCSuBf, Profile: debug) [2022-09-20T08:14:23Z WARN librespot_core::apresolve] Ignoring blacklisted access point ap-gew4.spotify.com:4070 [2022-09-20T08:14:23Z WARN librespot_core::apresolve] Ignoring blacklisted access point ap-gew4.spotify.com:443 [2022-09-20T08:14:23Z WARN librespot_core::apresolve] Ignoring blacklisted access point ap-gew4.spotify.com:80 [2022-09-20T08:14:23Z WARN librespot_core::apresolve] Ignoring blacklisted access point ap-gue1.spotify.com:443 [2022-09-20T08:14:23Z INFO librespot_core::session] Connecting to AP "ap-gae2.spotify.com:4070" [2022-09-20T08:14:25Z INFO librespot_core::session] Authenticated as "FooBar" ! [2022-09-20T08:14:25Z INFO librespot_core::session] Country: "DK" {"accessToken":"-removed-","expiresIn":3600}

What am I doing wrong?

with regards Nikolaj Hansen

michaelherger commented 1 year ago

Ok, this should actually be simple: compile with cargo build --release. The debug output is failing the parsing of the result.

NikolajHansen commented 1 year ago

oh so It tries to parse the debug output as part of the JSON payload? Maybe the debug info should be piped to a different buffer in place of stdout. Its really nice to have.

michaelherger commented 1 year ago

oh so It tries to parse the debug output as part of the JSON payload? Maybe the debug info should be piped to a different buffer in place of stdout. Its really nice to have.

Yes, the plug-in takes whatever output it gets and tries to parse it.

NikolajHansen commented 1 year ago

Fixed - thanks