starred/spotify-player

Fork 0

mirror of https://github.com/aome510/spotify-player.git synced 2026-04-26 17:35:50 +03:00

[GH-ISSUE #757] Device changer prompt not loading context #1385

New issue

Closed

opened 2026-03-14 14:36:27 +03:00 by kerem · 6 comments

kerem commented

2026-03-14 14:36:27 +03:00

Owner

Originally created by @OakTreeWC on GitHub (Jun 24, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/757

Describe the bug
When opening the Device changer prompt using "D", the prompt opens, but no context is shown within. Other devices are available.

To Reproduce
Open the device changer prompt (v0.20.6)

Expected behaviour
I expected the devices to load in.

Log and backtrace
2025-06-24T20:03:43.924988Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 158ms

Screenshots

Environment

OS: Ubuntu 24.04.2 LTS
Application version: v0.20.6

Additional context
Add any other context about the problem here.

Originally created by @OakTreeWC on GitHub (Jun 24, 2025). Original GitHub issue: https://github.com/aome510/spotify-player/issues/757 **Describe the bug** When opening the Device changer prompt using "D", the prompt opens, but no context is shown within. Other devices are available. **To Reproduce** Open the device changer prompt (v0.20.6) **Expected behaviour** I expected the devices to load in. **Log and backtrace** 2025-06-24T20:03:43.924988Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 158ms **Screenshots** ![Image](https://github.com/user-attachments/assets/a96d82b7-30be-47c5-ae9a-35b4f760cf38) **Environment** - OS: Ubuntu 24.04.2 LTS - Application version: v0.20.6 **Additional context** Add any other context about the problem here.

kerem

2026-03-14 14:36:27 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-14 14:36:44 +03:00

Author

Owner

@OakTreeWC commented on GitHub (Jun 24, 2025):

Update
Calling manually using authentication code from log results in blank response.

curl --request GET --url https://api.spotify.com/v1/me/player/devices --header 'Authorization: Bearer ...' { "devices" : [ ] }

Calling using authentication code from developer playground results in proper response.

@OakTreeWC commented on GitHub (Jun 24, 2025): **Update** Calling manually using authentication code from log results in blank response. ` curl --request GET --url https://api.spotify.com/v1/me/player/devices --header 'Authorization: Bearer ...' { "devices" : [ ] } ` Calling using authentication code from developer playground results in proper response.

kerem commented

2026-03-14 14:36:49 +03:00

Author

Owner

@OakTreeWC commented on GitHub (Jun 24, 2025):

Log Excerpt
2025-06-24T20:10:10.704876Z INFO spotify_player::token: Got new token: Token { access_token: "...", expires_in: TimeDelta { secs: 3600, nanos: 0 }, expires_at: Some(2025-06-24T21:10:10.704866812Z), refresh_token: None, **scopes: {}** }

No scopes appear to have been requested, causing no data to be shown?

Scopes are required for proper playback however...

@OakTreeWC commented on GitHub (Jun 24, 2025): **Log Excerpt** `2025-06-24T20:10:10.704876Z INFO spotify_player::token: Got new token: Token { access_token: "...", expires_in: TimeDelta { secs: 3600, nanos: 0 }, expires_at: Some(2025-06-24T21:10:10.704866812Z), refresh_token: None, **scopes: {}** }` No scopes appear to have been requested, causing no data to be shown? Scopes are required for proper playback however...

kerem commented

2026-03-14 14:36:54 +03:00

Author

Owner

@aome510 commented on GitHub (Jun 24, 2025):

Did you setup https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect? There should be a log line saying

No device found. Please make sure you already setup Spotify Connect support as described in https://github.com/aome510/spotify-player#spotify-connect

@aome510 commented on GitHub (Jun 24, 2025): Did you setup https://github.com/aome510/spotify-player?tab=readme-ov-file#spotify-connect? There should be a log line saying ``` No device found. Please make sure you already setup Spotify Connect support as described in https://github.com/aome510/spotify-player#spotify-connect ```

kerem commented

2026-03-14 14:36:59 +03:00

Author

Owner

@OakTreeWC commented on GitHub (Jun 24, 2025):

Oh, when I made the issue I was running the prebuilt software...
Yes I do see that log line.

I've modified the toml with my own client ID and built the application, however I'm still getting no device output, and looking in the log files and using the auth code from there the same blank output is given. I've tried putting the app.toml file in the original directory as well but nothing has changed. I also tried modifying the CLIENT_ID directly in the auth.rs file, to no avail.

@OakTreeWC commented on GitHub (Jun 24, 2025): Oh, when I made the issue I was running the prebuilt software... Yes I do see that log line. I've modified the toml with my own client ID and built the application, however I'm still getting no device output, and looking in the log files and using the auth code from there the same blank output is given. I've tried putting the app.toml file in the original directory as well but nothing has changed. I also tried modifying the CLIENT_ID directly in the auth.rs file, to no avail.

kerem commented

2026-03-14 14:37:04 +03:00

Author

Owner

@aome510 commented on GitHub (Jun 25, 2025):

Oh, when I made the issue I was running the prebuilt software... Yes I do see that log line.

I've modified the toml with my own client ID and built the application, however I'm still getting no device output, and looking in the log files and using the auth code from there the same blank output is given. I've tried putting the app.toml file in the original directory as well but nothing has changed. I also tried modifying the CLIENT_ID directly in the auth.rs file, to no avail.

You don't need to rebuild the app upon updating the config file. I think you might have changed the wrong toml file. Ensure changing the correct one in $HOME/.config/spotify_player/app.toml not the one in the repository. You can double check if the configs are updated by looking into the first few lines the log file. There should be a line printing all the parsed configs.

If everything is correct, then I don't know why you encountered the above issue

@aome510 commented on GitHub (Jun 25, 2025): > Oh, when I made the issue I was running the prebuilt software... Yes I do see that log line. > > I've modified the toml with my own client ID and built the application, however I'm still getting no device output, and looking in the log files and using the auth code from there the same blank output is given. I've tried putting the app.toml file in the original directory as well but nothing has changed. I also tried modifying the CLIENT_ID directly in the auth.rs file, to no avail. You don't need to rebuild the app upon updating the config file. I think you might have changed the wrong `toml` file. Ensure changing the correct one in `$HOME/.config/spotify_player/app.toml` **not the one in the repository**. You can double check if the configs are updated by looking into the first few lines the log file. There should be a line printing all the parsed configs. If everything is correct, then I don't know why you encountered the above issue

kerem commented

2026-03-14 14:37:09 +03:00

Author

Owner

@OakTreeWC commented on GitHub (Jun 25, 2025):

Ohhhhh.... I am actually blind. Yes upon moving the app.toml to $HOME/.config/spotify_player/app.toml and reinstalling spotify_player it did work. Thank you so much.

@OakTreeWC commented on GitHub (Jun 25, 2025): Ohhhhh.... I am actually blind. Yes upon moving the app.toml to `$HOME/.config/spotify_player/app.toml` and reinstalling spotify_player it did work. Thank you so much.