[GH-ISSUE #580] [bug] Authentication Issues #1272

Closed
opened 2026-03-14 14:11:20 +03:00 by kerem · 4 comments
Owner

Originally created by @w-lfchen on GitHub (Oct 23, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/580

this issue is a write-up of #520 due to that issue being way too long and tiring to read.

summary

spotify deprecated the login api used for authentication.
therefore, it is currently impossible to log in with the existing master branch/any version of spotify-player
a fix is being worked on in #570, the pr can be used for basic functionality, some issues remain.
feel free to contribute by working on the pr or submitting new problems that arise when using spotify-player built from it!

workaround

in an environment with a (somewhat up to date) rust toolchain set up, run the following commands in your home directory:

# build the librespot binary, we need this to generate credentials
git clone https://github.com/librespot-org/librespot.git
cd librespot
cargo build --release --no-default-features
# generate the credentials by running the program we just built
./target/release/librespot --cache ~/.cache/spotify-player/ -j
# Open or copy a link and login to Spotify as usual (this is the new login flow)
...
# cleanup once you've successfully logged in
cd ~
rm -rf ./librespot
# you should now be able to run spotify-player
spotify_player

huge thanks to the original authors and the modification! ❤️

technical details

spotify now requires an oauth2 login flow, which needs to implemented.
the library used for authentication is librespot, the dependency needs to be updated to the latest release which adds support for oauth2.
since that release contains a lot of breaking changes and the login flow in this application needs to be rewritten, this requires a substantial amount of work.
see #570 for the current state/progress made so far on fixing this situation.

Originally created by @w-lfchen on GitHub (Oct 23, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/580 this issue is a write-up of #520 due to that issue being way too long and tiring to read. ## summary spotify deprecated the login api used for authentication. **therefore, it is currently impossible to log in with the existing master branch/any version of spotify-player** a fix is being worked on in #570, the pr can be used for basic functionality, some issues remain. feel free to contribute by working on the pr or submitting new problems that arise when using spotify-player built from it! ## workaround in an environment with a (somewhat up to date) rust toolchain set up, run the following commands in your home directory: ```sh # build the librespot binary, we need this to generate credentials git clone https://github.com/librespot-org/librespot.git cd librespot cargo build --release --no-default-features # generate the credentials by running the program we just built ./target/release/librespot --cache ~/.cache/spotify-player/ -j # Open or copy a link and login to Spotify as usual (this is the new login flow) ... # cleanup once you've successfully logged in cd ~ rm -rf ./librespot # you should now be able to run spotify-player spotify_player ``` huge thanks to the [original authors](https://github.com/aome510/spotify-player/issues/520#issuecomment-2389486176) and the [modification](https://github.com/aome510/spotify-player/issues/520#issuecomment-2407187864)! :heart: ## technical details spotify now requires an oauth2 login flow, which needs to implemented. the library used for authentication is [librespot](https://github.com/librespot-org/librespot), the dependency needs to be updated to the latest release which adds support for oauth2. since that release contains a lot of breaking changes and the login flow in this application needs to be rewritten, this requires a substantial amount of work. see #570 for the current state/progress made so far on fixing this situation.
kerem 2026-03-14 14:11:20 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@w-lfchen commented on GitHub (Oct 23, 2024):

@w-lfchen read #581

doesn't exist..?

<!-- gh-comment-id:2433327711 --> @w-lfchen commented on GitHub (Oct 23, 2024): > @w-lfchen read #581 doesn't exist..?
Author
Owner

@Guimarret commented on GitHub (Oct 23, 2024):

The workaround worked ty!

<!-- gh-comment-id:2433356181 --> @Guimarret commented on GitHub (Oct 23, 2024): The workaround worked ty!
Author
Owner

@w-lfchen commented on GitHub (Oct 23, 2024):

@WantedToBeAnonymous i don't. i never reported you and even if i did, i wouldn't "owe" you anything.

your account @ManiArasteh was most likely banned due to inappropriate behavior. i am 99% sure that circumventing bans (which seems to be what you're doing right) now is against github's tos as well but i don't have the time to report you.

i am not putting up with this anymore.
get blocked, please leave me/us alone and in peace and have a nice day.

i've hidden this comment as off-topic because it is and i never wanted to discuss this on this issue but here we are.

<!-- gh-comment-id:2433748468 --> @w-lfchen commented on GitHub (Oct 23, 2024): @WantedToBeAnonymous i don't. i never reported you and even if i did, i wouldn't "owe" you anything. your account @ManiArasteh was most likely banned due to inappropriate behavior. i am 99% sure that circumventing bans (which seems to be what you're doing right) now is against github's tos as well but i don't have the time to report you. i am not putting up with this anymore. get blocked, please leave me/us alone and in peace and have a nice day. i've hidden this comment as off-topic because it is and i never wanted to discuss this on this issue but here we are.
Author
Owner

@MrGibus commented on GitHub (Oct 25, 2024):

Used the workaround and spotify reset my password.
If anyone else has this issue you won't be able to rerun unless you delete ~/.cache/spotify-player

<!-- gh-comment-id:2436776829 --> @MrGibus commented on GitHub (Oct 25, 2024): Used the workaround and spotify reset my password. If anyone else has this issue you won't be able to rerun unless you delete ~/.cache/spotify-player
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#1272
No description provided.