starred/spotify-player

Fork 0

mirror of https://github.com/aome510/spotify-player.git synced 2026-04-26 09:25:49 +03:00

[GH-ISSUE #912] Playback display not showing in TUI "No playback found." #552

New issue

Closed

opened 2026-03-02 23:48:36 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 23:48:36 +03:00

Owner

Originally created by @csoto-3 on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/912

Having the same issue as @lgeurts below.
Their comment was on a closed issue so I created a new one.

I can connect to my account and see listed devices.
Audio playback works if I switch device from my smartphone.
However I cannot control anything from the TUI, cannot browse my playlists, and the playback display does not work.

Using 0.21.2 installed via cargo with default features on a Win11 machine.

Same issue here. spotify-player 0.21.2-1. Can switch device and see it on my android phone. Audio plays on pc when selecting on phone. Other channels like YT play videos and sound flawlessly. Checked with alsa-mixer, pavucontrol and card is visble and works. As far as I can deduce the issue is the spotify_player software. Where is really goes wrong? No idea.
PS did a cargo run too. Added log.

2025-12-23T19:26:11.633009Z INFO spotify_player::auth: Using cached credentials
2025-12-23T19:26:11.633050Z INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "spotify-player", device_type: Speaker, is_group: false, initial_volume: 45875, disable_volume: false, volume_steps: 64 }
2025-12-23T19:26:11.633154Z INFO librespot_playback::mixer::softmixer: Mixing with softvol and volume control: Log(60.0)
2025-12-23T19:26:11.633203Z INFO spotify_player::streaming: Initializing a new integrated player with device_id=cbdcc9c9-99f3-4648-8398-c60054444f04
2025-12-23T19:26:11.633431Z INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol
2025-12-23T19:26:11.633558Z INFO librespot_playback::convert: Converting with ditherer: tpdf
2025-12-23T19:26:11.633583Z INFO librespot_playback::audio_backend::pulseaudio: Using PulseAudioSink with format: S16
2025-12-23T19:26:12.119449Z INFO librespot_core::session: Connecting to AP "ap-gew4.spotify.com:4070"
2025-12-23T19:26:12.307742Z INFO librespot_core::session: Authenticated as 'REMOVED' !
2025-12-23T19:26:12.307994Z INFO librespot_core::session: Country: "DE"
2025-12-23T19:26:12.778643Z INFO spotify_player::streaming: New streaming connection has been established!
2025-12-23T19:26:12.778667Z INFO spotify_player::client: Used a new session for Spotify client.
2025-12-23T19:26:12.778685Z INFO spotify_player::token: Getting a new authentication token...
2025-12-23T19:26:12.778702Z INFO spotify_player::token: Got new token: Token { access_token: "BQDGmOwzRp49xOcD1EhzaLgMNn-BvMur_MG5z6IRzREpLNa6bMmaybq77aamQ9hr-r7itgloYekH1a6_4BdFdwdDAtROxcU1jxrWLLM9NzGf6raXMpUNLYojUMTGJqkqqRHj9UbiEbN0w4WoDg1Ih_tVIcIq_HPyRbgQd5FVaYsKMvycEuI5A0lZYfRPZg4jWRvqKNZCilOJbL99saQvQ6L6lly1nFeMaCSUU21j425R1Jr890kOCPYM5yJn8CGHwKJpL_6MkBxCLf2v8aFD773Jmp3xd70RTK_eZYRoVcPqqnwGuW_hBp1odQKjXafwKbmmOs3U_-5LxbHq3QI010pciEqhXCt0tenfLT2Eb2z69bVT619ADFRc5TT7Vte_fO8T_Jo0zbN_LxpV8XUHiwKzchlzdw", expires_in: TimeDelta { secs: 3600, nanos: 0 }, expires_at: Some(2025-12-23T20:26:12.778701157Z), refresh_token: None, scopes: {} }
2025-12-23T19:26:12.779368Z INFO spotify_player: Starting a client socket at 127.0.0.1:8080
2025-12-23T19:26:12.779576Z INFO spotify_player::media_control: Initializing application's media control event watcher...
2025-12-23T19:26:13.012239Z ERROR client_request{request=GetUserPlaylists}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/playlists: {
"error": {
"status": 429,
"message": "API rate limit exceeded"
}
}
2025-12-23T19:26:13.038422Z INFO librespot_core::spclient: Resolved "gew4-spclient.spotify.com:443" as spclient access point
2025-12-23T19:26:13.060352Z ERROR client_request{request=GetCurrentUser}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests
2025-12-23T19:26:13.060446Z ERROR client_request{request=GetUserSavedShows}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests
2025-12-23T19:26:13.060475Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests
2025-12-23T19:26:13.060501Z ERROR client_request{request=GetUserSavedAlbums}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests
2025-12-23T19:26:13.060526Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests
2025-12-23T19:26:13.531664Z INFO librespot_connect::spirc: active device is <> with session <14e6353fe4c5cfd3d7542158e8ce7c74>
2025-12-23T19:26:13.809193Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests
2025-12-23T19:26:13.809384Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests
2025-12-23T19:26:28.723821Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 370ms
2025-12-23T19:26:40.314568Z ERROR client_request{request=Player(TransferPlayback("cbdcc9c9-99f3-4648-8398-c60054444f04", false))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests
2025-12-23T19:26:45.143640Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 37ms
2025-12-23T19:27:05.678509Z WARN librespot_connect::state::context: couldn't load context info because: context is not available. type: Default
2025-12-23T19:27:05.857741Z INFO librespot_playback::player: Loading <Is It Any Wonder?> with Spotify URI spotify:track:5xT8JXJSyHYNfC11OFqzFL
2025-12-23T19:27:06.094218Z WARN librespot_playback::player: Invalid start position of 1375245 ms exceeds track's duration of 186173 ms, starting track from the beginning
2025-12-23T19:27:06.272871Z INFO librespot_playback::player: <Is It Any Wonder?> (186173 ms) loaded
2025-12-23T19:27:06.273227Z INFO spotify_player::streaming: Got a new player event: Changed { playable_id: Track(TrackId("5xT8JXJSyHYNfC11OFqzFL")) }
2025-12-23T19:27:06.303439Z INFO spotify_player::streaming: Got a new player event: Playing { playable_id: Track(TrackId("5xT8JXJSyHYNfC11OFqzFL")), position_ms: 0 }
2025-12-23T19:27:07.343926Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests
2025-12-23T19:27:07.344065Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests
2025-12-23T19:27:08.369901Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests
2025-12-23T19:27:08.370107Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests
2025-12-23T19:27:09.393389Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests

Originally posted by @lgeurts in #284

Originally created by @csoto-3 on GitHub (Jan 14, 2026). Original GitHub issue: https://github.com/aome510/spotify-player/issues/912 Having the same issue as @lgeurts below. Their comment was on a closed issue so I created a new one. I can connect to my account and see listed devices. Audio playback works if I switch device from my smartphone. However I cannot control anything from the TUI, cannot browse my playlists, and the playback display does not work. Using 0.21.2 installed via cargo with default features on a Win11 machine. > Same issue here. spotify-player 0.21.2-1. Can switch device and see it on my android phone. Audio plays on pc when selecting on phone. Other channels like YT play videos and sound flawlessly. Checked with alsa-mixer, pavucontrol and card is visble and works. As far as I can deduce the issue is the spotify_player software. Where is really goes wrong? No idea. > PS did a cargo run too. Added log. > > 2025-12-23T19:26:11.633009Z INFO spotify_player::auth: Using cached credentials > 2025-12-23T19:26:11.633050Z INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "spotify-player", device_type: Speaker, is_group: false, initial_volume: 45875, disable_volume: false, volume_steps: 64 } > 2025-12-23T19:26:11.633154Z INFO librespot_playback::mixer::softmixer: Mixing with softvol and volume control: Log(60.0) > 2025-12-23T19:26:11.633203Z INFO spotify_player::streaming: Initializing a new integrated player with device_id=cbdcc9c9-99f3-4648-8398-c60054444f04 > 2025-12-23T19:26:11.633431Z INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol > 2025-12-23T19:26:11.633558Z INFO librespot_playback::convert: Converting with ditherer: tpdf > 2025-12-23T19:26:11.633583Z INFO librespot_playback::audio_backend::pulseaudio: Using PulseAudioSink with format: S16 > 2025-12-23T19:26:12.119449Z INFO librespot_core::session: Connecting to AP "ap-gew4.spotify.com:4070" > 2025-12-23T19:26:12.307742Z INFO librespot_core::session: Authenticated as 'REMOVED' ! > 2025-12-23T19:26:12.307994Z INFO librespot_core::session: Country: "DE" > 2025-12-23T19:26:12.778643Z INFO spotify_player::streaming: New streaming connection has been established! > 2025-12-23T19:26:12.778667Z INFO spotify_player::client: Used a new session for Spotify client. > 2025-12-23T19:26:12.778685Z INFO spotify_player::token: Getting a new authentication token... > 2025-12-23T19:26:12.778702Z INFO spotify_player::token: Got new token: Token { access_token: "BQDGmOwzRp49xOcD1EhzaLgMNn-BvMur_MG5z6IRzREpLNa6bMmaybq77aamQ9hr-r7itgloYekH1a6_4BdFdwdDAtROxcU1jxrWLLM9NzGf6raXMpUNLYojUMTGJqkqqRHj9UbiEbN0w4WoDg1Ih_tVIcIq_HPyRbgQd5FVaYsKMvycEuI5A0lZYfRPZg4jWRvqKNZCilOJbL99saQvQ6L6lly1nFeMaCSUU21j425R1Jr890kOCPYM5yJn8CGHwKJpL_6MkBxCLf2v8aFD773Jmp3xd70RTK_eZYRoVcPqqnwGuW_hBp1odQKjXafwKbmmOs3U_-5LxbHq3QI010pciEqhXCt0tenfLT2Eb2z69bVT619ADFRc5TT7Vte_fO8T_Jo0zbN_LxpV8XUHiwKzchlzdw", expires_in: TimeDelta { secs: 3600, nanos: 0 }, expires_at: Some(2025-12-23T20:26:12.778701157Z), refresh_token: None, scopes: {} } > 2025-12-23T19:26:12.779368Z INFO spotify_player: Starting a client socket at 127.0.0.1:8080 > 2025-12-23T19:26:12.779576Z INFO spotify_player::media_control: Initializing application's media control event watcher... > 2025-12-23T19:26:13.012239Z ERROR client_request{request=GetUserPlaylists}: spotify_player::client::handlers: Failed to handle client request: failed to send a Spotify API request https://api.spotify.com/v1/me/playlists: { > "error": { > "status": 429, > "message": "API rate limit exceeded" > } > } > 2025-12-23T19:26:13.038422Z INFO librespot_core::spclient: Resolved "gew4-spclient.spotify.com:443" as spclient access point > 2025-12-23T19:26:13.060352Z ERROR client_request{request=GetCurrentUser}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests > 2025-12-23T19:26:13.060446Z ERROR client_request{request=GetUserSavedShows}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests > 2025-12-23T19:26:13.060475Z ERROR client_request{request=GetUserFollowedArtists}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests > 2025-12-23T19:26:13.060501Z ERROR client_request{request=GetUserSavedAlbums}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests > 2025-12-23T19:26:13.060526Z ERROR client_request{request=GetUserSavedTracks}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests > 2025-12-23T19:26:13.531664Z INFO librespot_connect::spirc: active device is <> with session <14e6353fe4c5cfd3d7542158e8ce7c74> > 2025-12-23T19:26:13.809193Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests > 2025-12-23T19:26:13.809384Z ERROR spotify_player::client: Failed to retrieve current playback: http error: status code 429 Too Many Requests > 2025-12-23T19:26:28.723821Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 370ms > 2025-12-23T19:26:40.314568Z ERROR client_request{request=Player(TransferPlayback("cbdcc9c9-99f3-4648-8398-c60054444f04", false))}: spotify_player::client::handlers: Failed to handle client request: http error: status code 429 Too Many Requests > 2025-12-23T19:26:45.143640Z INFO client_request{request=GetDevices}: spotify_player::client: Successfully handled the client request, took: 37ms > 2025-12-23T19:27:05.678509Z WARN librespot_connect::state::context: couldn't load context info because: context is not available. type: Default > 2025-12-23T19:27:05.857741Z INFO librespot_playback::player: Loading <Is It Any Wonder?> with Spotify URI <spotify:track:5xT8JXJSyHYNfC11OFqzFL> > 2025-12-23T19:27:06.094218Z WARN librespot_playback::player: Invalid start position of 1375245 ms exceeds track's duration of 186173 ms, starting track from the beginning > 2025-12-23T19:27:06.272871Z INFO librespot_playback::player: <Is It Any Wonder?> (186173 ms) loaded > 2025-12-23T19:27:06.273227Z INFO spotify_player::streaming: Got a new player event: Changed { playable_id: Track(TrackId("5xT8JXJSyHYNfC11OFqzFL")) } > 2025-12-23T19:27:06.303439Z INFO spotify_player::streaming: Got a new player event: Playing { playable_id: Track(TrackId("5xT8JXJSyHYNfC11OFqzFL")), position_ms: 0 } > 2025-12-23T19:27:07.343926Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests > 2025-12-23T19:27:07.344065Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests > 2025-12-23T19:27:08.369901Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests > 2025-12-23T19:27:08.370107Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests > 2025-12-23T19:27:09.393389Z ERROR spotify_player::client: Encountered an error when updating the playback state: http error: status code 429 Too Many Requests > > _Originally posted by @lgeurts in [#284](https://github.com/aome510/spotify-player/issues/284#issuecomment-3687784058)_

kerem

2026-03-02 23:48:36 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 23:48:37 +03:00

Author

Owner

@mttgl commented on GitHub (Jan 14, 2026):

Also having this error- fresh install from cargo on both Windows 11 and Mac OS Sequoia, as well as directly downloaded from github release.

@mttgl commented on GitHub (Jan 14, 2026): Also having this error- fresh install from cargo on both Windows 11 and Mac OS Sequoia, as well as directly downloaded from github release.

kerem commented

2026-03-02 23:48:37 +03:00

Author

Owner

@mttgl commented on GitHub (Jan 14, 2026):

Figured out a workaround for the newest release. After installation, run, then cancel before authorization.

Open up the app.toml located at ~/.config/spotify-player/app.toml and manually change client_id to the client_id from your developer account on Spotify.

Re-run and press d on the main screen to select the spotify_player device as a sound output target and everything seems to be working now.

Might be worth it to put something in the project readme so that new users are aware there are some issues going on that are outside the developer's control.

@mttgl commented on GitHub (Jan 14, 2026): Figured out a workaround for the newest release. After installation, run, then cancel before authorization. Open up the `app.toml` located at `~/.config/spotify-player/app.toml` and manually change `client_id` to the `client_id` from your developer account on Spotify. Re-run and press `d` on the main screen to select the spotify_player device as a sound output target and everything seems to be working now. Might be worth it to put something in the project readme so that new users are aware there are some issues going on that are outside the developer's control.

kerem commented

2026-03-02 23:48:37 +03:00

Author

Owner

@cuppajoeman commented on GitHub (Jan 22, 2026):

I also had this issue. A few notes:

I wasn't able to create a new application on the spotify devloper page because apparently they were modifying their api or something, I was lucky enough to have an old one that I repurposed for this.
If you already tried logging in regularly there will already be a value in client_id in app.toml, I replaced that with the new one.
I tried launching it again and it didn't work I got: Error: initialize new Spotify session which I solved via: rm -rf $HOME/.cache/spotify-player/* which removes the data associated with the old session.
Then launching the app just worked, I went through the browser authentication and then after that everything immediately started loading.

@cuppajoeman commented on GitHub (Jan 22, 2026): I also had this issue. A few notes: - I wasn't able to create a new application on the spotify devloper page because apparently they were modifying their api or something, I was lucky enough to have an old one that I repurposed for this. - If you already tried logging in regularly there will already be a value in client_id in app.toml, I replaced that with the new one. - I tried launching it again and it didn't work I got: [Error: initialize new Spotify session](https://github.com/aome510/spotify-player/issues/837#top) which I solved via: `rm -rf $HOME/.cache/spotify-player/*` which removes the data associated with the old session. - Then launching the app just worked, I went through the browser authentication and then after that everything immediately started loading.

kerem commented

2026-03-02 23:48:37 +03:00

Author

Owner

@titu3e commented on GitHub (Jan 23, 2026):

I also had this issue. A few notes:

I wasn't able to create a new application on the spotify devloper page because apparently they were modifying their api or something, I was lucky enough to have an old one that I repurposed for this.

If you already tried logging in regularly there will already be a value in client_id in app.toml, I replaced that with the new one.

I tried launching it again and it didn't work I got: Error: initialize new Spotify session which I solved via: rm -rf $HOME/.cache/spotify-player/* which removes the data associated with the old session.

Then launching the app just worked, I went through the browser authentication and then after that everything immediately started loading.

did u have the clinet id of the same account u wanted to login with? cuz as u said i wasnt able to create a new app in the dev dashboard so i used the one i had before of another account . but i get a 403 forbidden error

@titu3e commented on GitHub (Jan 23, 2026): > I also had this issue. A few notes: > > * I wasn't able to create a new application on the spotify devloper page because apparently they were modifying their api or something, I was lucky enough to have an old one that I repurposed for this. > * If you already tried logging in regularly there will already be a value in client_id in app.toml, I replaced that with the new one. > * I tried launching it again and it didn't work I got: [Error: initialize new Spotify session](https://github.com/aome510/spotify-player/issues/837#top) which I solved via: `rm -rf $HOME/.cache/spotify-player/*` which removes the data associated with the old session. > * Then launching the app just worked, I went through the browser authentication and then after that everything immediately started loading. did u have the clinet id of the same account u wanted to login with? cuz as u said i wasnt able to create a new app in the dev dashboard so i used the one i had before of another account . but i get a 403 forbidden error

kerem commented

2026-03-02 23:48:37 +03:00

Author

Owner

@nicobrenner commented on GitHub (Jan 29, 2026):

I'm having this same issue, spotify_player 0.21.3 installed via Homebrew on MacOS Sequoia, Apple M3. I can select spotify_player as a device from Spotify and I get audio playing through it, but the TUI is pretty much empty and I can't control playback. Pressing D opens up an empty Devices tab/dialog.

Also, it used to be (maybe version 0.20.4), that when starting spotify_player it would automatically switch my Spotify's account playback device, ie. I didn't need to manually select it

About the potential fix, I just created a developer account, but I can't create an app

@nicobrenner commented on GitHub (Jan 29, 2026): I'm having this same issue, `spotify_player 0.21.3` installed via Homebrew on MacOS Sequoia, Apple M3. I can select spotify_player as a device from Spotify and I get audio playing through it, but the TUI is pretty much empty and I can't control playback. Pressing `D` opens up an empty Devices tab/dialog. Also, it used to be (maybe version 0.20.4), that when starting `spotify_player` it would automatically switch my Spotify's account playback device, ie. I didn't need to manually select it About the potential fix, I just created a developer account, but I can't create an app <img width="496" height="148" alt="Image" src="https://github.com/user-attachments/assets/08a6eed3-0fff-49db-9ed3-7449d0b8d4ba" />

kerem referenced this issue

2026-03-02 23:49:52 +03:00

[PR #552] [MERGED] implement podcast functionality #795

kerem referenced this issue

2026-03-14 15:30:11 +03:00

[PR #552] [MERGED] implement podcast functionality #1734