Closed alepee closed 7 years ago
You need to run git pull
. Then run cargo clean &&a cargo build
That should be cargo clean && cargo build
is this linked to rand
update? https://github.com/plietar/librespot/compare/aa86ebf...master#diff-80398c5faae3c069e4e6aa2ed11b28c0R65
anyway it seems to work properly on every connection tentative. Thanks @sashahilton00
@alepee nope, linked to the fact that Spotify requested that it identify as librespot and not as 'This is not the client you are looking for', so they blocked the latter. the git pull got the PR that fixed identification, and the cargo clean && build built it.
I reproduced it even with a fresh build.
This happens even with direct login, cache enable and/or any other option. It will eventually work after a few tries.
For example
lon3-accesspoint-a2.ap.spotify.com:4070
works but notlon6-accesspoint-a33.ap.spotify.com:4070
Any guess?
PS: I don't have more details even with env var RUST_BACKTRACE set to 1