mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #804] Device list shows blank #1415
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#1415
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 @arashdev7 on GitHub (Aug 13, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/804
Describe the bug
It was appearing untill yesterday, I don't know what the problem is. spotifyd and spotify player both are showing as devices on my phone and I can har audio thrugh my laptop if i select them through my phone
To Reproduce
My laptop fell, so maybe that lmao, but everything else is working so I don't think that is the problem
Expected behaviour
the devices to show
Log and backtrace
Log and backtrace of a run reproducing the bug to help debug the issue, which are usually located in
$HOME/.cache/spotify-player/.Please refer to this URL for more details.
Screenshots
Environment
spotify_playerAdditional context
Add any other context about the problem here.
@MaqxG commented on GitHub (Aug 13, 2025):
I have the same problem since today.
I also don't seem to be able to load any playlist or search for a song. Playlists keep hanging on Loading... And with search I can type the name of a song, but it doesn't show anything.
I have tried to reauthenticate and reinstall spotify_player, but that didn't help.
I'm running spotify_player v0.20.7 from crates.io on Ubuntu 24.04.3
@aome510 commented on GitHub (Aug 13, 2025):
Spotify recently made a few breaking changes to the APIs, making
spotify_playernot function correctly. SeePlease include applicable logs, otherwise people won't be able to tell what is the cause of this issue, which might be related to the two issues linked above
@arashdev7 commented on GitHub (Aug 13, 2025):
spotify_player_clean_1.log
Sorrrry my bad ( >_< ), I am relatively new to linux, I have attached the log I created using the tee command, and I cleared using asci2txt, let me know if something else is required
@jasht1 commented on GitHub (Aug 13, 2025):
I was having the issue described in #796 where the app appears to work but plays no audio, while troubleshooting this I reinstalled the app via
cargo install spotify_player --features image,notify,fzf,media-controland now appear to have this issue, all the sub windows are blank apart from "Artists" and I'm unable to select a device.From the logs it looks like a manifestation of #802 where spotify_player is unable to attain an authentication token from spotify.
I've attached the full log with my ID redacted to this post.
spotify-player_PUBLIC.log
@aome510 commented on GitHub (Aug 13, 2025):
Oh I mean the application's log not the terminal log. See https://github.com/aome510/spotify-player?tab=readme-ov-file#logging
yes, it's another new issue reported by people yesterday. See https://github.com/aome510/spotify-player/issues/802. They seem to have a workaround mentioned in the thread, but I haven't tested it myself
@Montero1905 commented on GitHub (Aug 14, 2025):
I'm having the same issue here. macOS. I'm using the fork described in #802 unsuccessfully. The integrated client works fine but spotify_player doesn't seem to be using my client_id to have a full spotify connect.
@arashdev7 commented on GitHub (Aug 17, 2025):
25-08-17T12:10:07.224958Z WARN librespot_core::apresolve: Failed to resolve all access points, using fallbacks
2025-08-17T12:10:07.225014Z WARN librespot_core::apresolve: Resolve access points error: Service unavailable { client error (Connect) }
2025-08-17T12:10:07.225033Z INFO librespot_core::session: Connecting to AP "ap.spotify.com:443"
2025-08-17T12:10:07.709899Z INFO librespot_core::session: Authenticated as 'arashdev' !
2025-08-17T12:10:07.710440Z INFO librespot_core::session: Country: "IN"
2025-08-17T12:10:07.712215Z INFO spotify_player::streaming: New streaming connection has been established!
2025-08-17T12:10:07.712254Z INFO spotify_player::client: Used a new session for Spotify client.
2025-08-17T12:10:07.712335Z INFO spotify_player::token: Getting a new authentication token...
2025-08-17T12:10:07.856487Z ERROR librespot_core::mercury: error 403 for uri hm://keymaster/token/authenticated?scope=user-read-recently-played,user-top-read,user-read-playback-position,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,streaming,playlist-read-private,playlist-modify-private,playlist-modify-public,playlist-read-collaborative,user-follow-read,user-follow-modify,user-library-read,user-library-modify&client_id=65b708073fc0480ea92a077233ca87bd&device_id=451f456a-5fb1-44a0-b010-ebf8587eb1ea
2025-08-17T12:10:07.856616Z ERROR spotify_player::client::spotify: Failed to get a new token: failed to get the token: Service unavailable { error handling Mercury response: MercuryResponse { uri: "hm://keymaster/token/authenticated?scope=user-read-recently-played,user-top-read,user-read-playback-position,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,streaming,playlist-read-private,playlist-modify-private,playlist-modify-public,playlist-read-collaborative,user-follow-read,user-follow-modify,user-library-read,user-library-modify&client_id=65b708073fc0480ea92a077233ca87bd&device_id=451f456a-5fb1-44a0-b010-ebf8587eb1ea", status_code: 403, payload: 123, 34, 99, 111, 100, 101, 34, 58, 52, 44, 34, 101, 114, 114, 111, 114, 68, 101, 115, 99, 114, 105, 112, 116, 105, 111, 110, 34, 58, 34, 73, 110, 118, 97, 108, 105, 100, 32, 114, 101, 113, 117, 101, 115, 116, 34, 125 } }
2025-08-17T12:10:07.856906Z INFO spotify_player: Starting a client socket at 127.0.0.1:8080
2025-08-17T12:10:07.857167Z INFO spotify_player::media_control: Initializing application's media control event watcher...
2025-08-17T12:10:07.858084Z INFO client_request{request=GetUserPlaylists}: spotify_player::token: Getting a new authentication token...
2025-08-17T12:10:07.858164Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: Token is not valid
2025-08-17T12:10:07.858166Z ERROR client_request{request=GetCurrentUser}: spotify_player::client::handlers: Failed to handle client request: Token is not valid
2025-08-17T12:10:07.858166Z ERROR client_request{request=GetUserSavedAlbums}: spotify_player::client::handlers: Failed to handle client request: Token is not valid
2025-08-17T12:10:07.858167Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: Token is not valid
2025-08-17T12:10:07.858166Z ERROR client_request{request=GetUserSavedShows}: spotify_player::client::handlers: Failed to handle client request: Token is not valid
2025-08-17T12:10:08.075819Z ERROR librespot_core::mercury: error 403 for uri hm://keymaster/token/authenticated?scope=user-read-recently-played,user-top-read,user-read-playback-position,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,streaming,playlist-read-private,playlist-modify-private,playlist-modify-public,playlist-read-collaborative,user-follow-read,user-follow-modify,user-library-read,user-library-modify&client_id=65b708073fc0480ea92a077233ca87bd&device_id=451f456a-5fb1-44a0-b010-ebf8587eb1ea
2025-08-17T12:10:08.075947Z ERROR client_request{request=GetUserPlaylists}: spotify_player::client::spotify: Failed to get a new token: failed to get the token: Service unavailable { error handling Mercury response: MercuryResponse { uri: "hm://keymaster/token/authenticated?scope=user-read-recently-played,user-top-read,user-read-playback-position,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,streaming,playlist-read-private,playlist-modify-private,playlist-modify-public,playlist-read-collaborative,user-follow-read,user-follow-modify,user-library-read,user-library-modify&client_id=65b708073fc0480ea92a077233ca87bd&device_id=451f456a-5fb1-44a0-b010-ebf8587eb1ea", status_code: 403, payload: 123, 34, 99, 111, 100, 101, 34, 58, 52, 44, 34, 101, 114, 114, 111, 114, 68, 101, 115, 99, 114, 105, 112, 116, 105, 111, 110, 34, 58, 34, 73, 110, 118, 97, 108, 105, 100, 32, 114, 101, 113, 117, 101, 115, 116, 34, 125 } }
2025-08-17T12:10:08.075967Z ERROR client_request{request=GetUserPlaylists}: spotify_player::client::handlers: Failed to handle client request: get access token: failed to get the authentication token stored inside the client.
2025-08-17T12:10:08.857322Z ERROR spotify_player::client: Failed to retrieve current playback: Token is not valid
2025-08-17T12:10:08.857356Z ERROR spotify_player::client: Failed to retrieve current playback: Token is not valid
2025-08-17T12:10:10.469731Z ERROR librespot_core::mercury: error 403 for uri hm://keymaster/token/authenticated?scope=user-read-recently-played,user-top-read,user-read-playback-position,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,streaming,playlist-read-private,playlist-modify-private,playlist-modify-public,playlist-read-collaborative,user-follow-read,user-follow-modify,user-library-read,user-library-modify&client_id=7659e3d0f1cf4eda8203d9a49b8bc1be&device_id=451f456a-5fb1-44a0-b010-ebf8587eb1ea
2025-08-17T12:10:10.469841Z ERROR client_request{request=GetDevices}: spotify_player::client::handlers: Failed to handle client request: get access token: Service unavailable { error handling Mercury response: MercuryResponse { uri: "hm://keymaster/token/authenticated?scope=user-read-recently-played,user-top-read,user-read-playback-position,user-read-playback-state,user-modify-playback-state,user-read-currently-playing,streaming,playlist-read-private,playlist-modify-private,playlist-modify-public,playlist-read-collaborative,user-follow-read,user-follow-modify,user-library-read,user-library-modify&client_id=7659e3d0f1cf4eda8203d9a49b8bc1be&device_id=451f456a-5fb1-44a0-b010-ebf8587eb1ea", status_code: 403, payload: 123, 34, 99, 111, 100, 101, 34, 58, 52, 44, 34, 101, 114, 114, 111, 114, 68, 101, 115, 99, 114, 105, 112, 116, 105, 111, 110, 34, 58, 34, 73, 110, 118, 97, 108, 105, 100, 32, 114, 101, 113, 117, 101, 115, 116, 34, 125 } }
Sorry for the delay this was the relevant log I found
@arashdev7 commented on GitHub (Aug 17, 2025):
Ok sir I followed comment #802 and I can see the playback but the device list still shows empty
@arashdev7 commented on GitHub (Aug 17, 2025):
2025-08-17T12:30:44.956670Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 122ms
2025-08-17T12:31:00.283410Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 210ms
it shows it handled the request perfectly but I can't see any devices
@arashdev7 commented on GitHub (Aug 17, 2025):
@aome510 commented on GitHub (Aug 17, 2025):
Did you go through https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect? There should be a log line pointing to the above document if the API works and no device is returned
@arashdev7 commented on GitHub (Aug 18, 2025):
Yeah I went through it, the config I have is pretty similar to example config and I made the spotify app accordingly I think, I'll go through again and will get back
@ThomasTheCoder198 commented on GitHub (Aug 20, 2025):
Have someone fixed this ?
@dcorral commented on GitHub (Aug 21, 2025):
@dcorral commented on GitHub (Aug 21, 2025):
Looks like the access token scope/permissions are wrong.
https://developer.spotify.com/documentation/web-api/reference/get-a-users-available-devices
I used the access token logged in the app logs in the sample curl call provided above and it returns a valid response (200) but with an empty array:
if I use the access token in the example in the documentation I get the full list of devices.
So that makes me think there is something off with the access token generation/fetch. This is also related to the recent issues on authentication #802
@sewnie commented on GitHub (Aug 23, 2025):
Unusable.
@bbzylstra commented on GitHub (Aug 23, 2025):
The new login5 token acquisition method unfortunately does not support custom client_ids (login5 uses the spotify keymaster id 65b708073fc0480ea92a077233ca87bd), so I think moving forward the device list will no longer work. https://github.com/librespot-org/librespot/issues/1532
If you want these features, you'd need to implement the spotify oauth flow with a custom client_id and client_secret.
@aome510 commented on GitHub (Aug 24, 2025):
Please refer to my comment in https://github.com/aome510/spotify-player/issues/802#issuecomment-3218342832. Will figure out how to bring back Spotify Connect
@aome510 commented on GitHub (Aug 25, 2025):
Should be fixed by #809. With the new change, users will be prompted once to get a new token (cached in
$APP_CACHE_FOLDER/user_client_token.json) for the Spotify Connect integration. Please refer to latest Spotify Connect doc for more details.Lmk if you guys have any issues
@dcorral commented on GitHub (Aug 25, 2025):
I can see the list of devices however only the default device set in the app.toml works
some logs in case it helps:
@aome510 commented on GitHub (Aug 25, 2025):
see https://github.com/aome510/spotify-player/issues/811
I can do Spotify Connect just fine to another device, i.e. my phone or Spotify official app. The problem is that
spotify_player's integrated player still plays the sound even the playback is transferred to a different device.