mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #876] spotify-player remains idle after connecting to "spotify-player" device #523
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#523
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Pommersche92 on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/876
Describe the bug
After setting everything up according to the readme, I can connect to a device called "spotify-player" in my spotify app when i have the spotify_player application running (where it shows an error message in the region "Playback" (see screenshot).
To Reproduce
set everything up according to readme. can connect to speaker. according to spotify the music is being played through the "spotify-player" speaker, but the terminal app is still saying "no playback found". D (to show devices in spotify-player toggles an empty devices list)
Expected behaviour
terminal app spotify-player starts playing the song and showing the info about playback, playlists,. albums, artists and everything else as the screenshots of this program suggest.
Log and backtrace
Log:
Backtrace is completely empty
Screenshots
Environment
Additional context
@NelDav commented on GitHub (Nov 17, 2025):
Since November 27, Spotify API does no longer accept localhost and http redirects. I think that is the problem: https://developer.spotify.com/blog/2025-10-14-reminder-oauth-migration-27-nov-2025
Edit: I think I was wrong. It looks like spotify_player already uses PCKE code:
github.com/aome510/spotify-player@6faa7803b1/spotify_player/src/client/mod.rs (L86)What I noticed is that the
client_idof the Mercury request is65b708073fc0480ea92a077233ca87bdin my log as well and that is not the one I entered in my config file. I am not sure if that is intended, but it seems a little bit odd.@NelDav commented on GitHub (Nov 17, 2025):
Ok, I found out. Version 0.20.7 is to old. This issues was already reported (https://github.com/aome510/spotify-player/issues/802) and fixed in version 0.21.0
There is a newer version on the Arch repository: https://archlinux.org/packages/extra/x86_64/spotify-player/
The problem is that even though the Arch repository offers the newest version, Manajaro repository (the stable branch) does not: https://manjaristas.org/branch_compare?q=spotify-player
I am not sure how often manjaro repository updates. However, I suggest installing spotify-player via cargo while Manjaro repository does contain the old spotify-player version.
@Pommersche92 commented on GitHub (Nov 18, 2025):
Ah, thank you for the info! Yeah, thats actually the reason i prefer manjaro to arch, not bleeding bleeding edge but reasonable bleeding edge... nnow that bit me in the ass... 😆