[GH-ISSUE #605] No Devices Appear in Device popup #354

Closed
opened 2026-03-02 23:46:49 +03:00 by kerem · 5 comments
Owner

Originally created by @OneBiteAidan on GitHub (Nov 14, 2024).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/605

Describe the bug
No devices (i.e bluetooth headphones, laptop speakers) show up in the devices menu after pressing D.

To Reproduce

  1. Clone the package via the AUR
  2. Open the app with spotify-player and follow the link to the login.
  3. Create a new spotify developer application.
  4. Copy the URI from the app.toml to the developer application.
  5. Copy the developer application's client_id to the app.toml file.
  6. Relaunch spotify-player after reboot

Expected behaviour
2 Devices should appear. My laptop's integrated speakers and my bluetooth headphones called 'Ground Control'.

Log and backtrace
log
Backtrace has no contents.

Environment

  • OS: Arch Linux
  • Application version: 0.20.1
  • Application features: N/A. No additional features added other than the ones that ship default with the AUR.

Additional context
Should I be worried about my access_token being shared in the logs provided above?

Originally created by @OneBiteAidan on GitHub (Nov 14, 2024). Original GitHub issue: https://github.com/aome510/spotify-player/issues/605 **Describe the bug** No devices (i.e bluetooth headphones, laptop speakers) show up in the devices menu after pressing D. **To Reproduce** 1. Clone the package via the [AUR](https://aur.archlinux.org/packages/spotify-player) 2. Open the app with spotify-player and follow the link to the login. 3. Create a new spotify developer application. 4. Copy the URI from the app.toml to the developer application. 5. Copy the developer application's client_id to the app.toml file. 6. Relaunch spotify-player after reboot **Expected behaviour** 2 Devices should appear. My laptop's integrated speakers and my bluetooth headphones called 'Ground Control'. **Log and backtrace** [log](https://pastebin.com/tvF8bdLp) Backtrace has no contents. **Environment** - OS: Arch Linux - Application version: 0.20.1 - Application features: N/A. No additional features added other than the ones that ship default with the AUR. **Additional context** Should I be worried about my access_token being shared in the logs provided above?
kerem 2026-03-02 23:46:49 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@hotln commented on GitHub (Nov 15, 2024):

Mate, I recommend modifying this issue and remove those logs because the access_token is visible and explicit.

<!-- gh-comment-id:2480116753 --> @hotln commented on GitHub (Nov 15, 2024): Mate, I recommend modifying this issue and remove those logs because the access_token is visible and explicit.
Author
Owner

@OneBiteAidan commented on GitHub (Nov 15, 2024):

Mate, I recommend modifying this issue and remove those logs because the access_token is visible and explicit.

Afaik, Spotify access tokens are only valid for 1hr. So it should be okay.

<!-- gh-comment-id:2480165292 --> @OneBiteAidan commented on GitHub (Nov 15, 2024): > Mate, I recommend modifying this issue and remove those logs because the access_token is visible and explicit. > Afaik, [Spotify access tokens are only valid for 1hr.](https://developer.spotify.com/documentation/web-api/concepts/access-token) So it should be okay.
Author
Owner

@hotln commented on GitHub (Nov 16, 2024):

Oh yeah, you are alright. I forgot about it. I'm still to deal with your bug but no luck so far. Let me know if you have any updates on it,

<!-- gh-comment-id:2480241678 --> @hotln commented on GitHub (Nov 16, 2024): Oh yeah, you are alright. I forgot about it. I'm still to deal with your bug but no luck so far. Let me know if you have any updates on it,
Author
Owner

@OneBiteAidan commented on GitHub (Nov 16, 2024):

Will do! I haven't touched it in a few days but I'll try some stuff out. Anything else I can do to assist you with this?

<!-- gh-comment-id:2480347261 --> @OneBiteAidan commented on GitHub (Nov 16, 2024): Will do! I haven't touched it in a few days but I'll try some stuff out. Anything else I can do to assist you with this?
Author
Owner

@aome510 commented on GitHub (Nov 18, 2024):

Hi, I think you mistook Spotify device with the actual physical device. "Device" here refers to an active Spotify client, which can be spotify_player's integrated client, Spotify Desktop app, or Spotify mobile app on your phone.

One thing I realized from your log is that there is no integrated client initialized on startup. Are you sure you run the application with the right set of features? Based on the log, I'm pretty sure that the streaming feature is not enabled. There should be lines as follows in the log at the beginning, which you can compare to yours to see the differences:

2024-11-04T15:35:19.854566Z  INFO spotify_player::state::data: Successfully loaded SavedTracks data!
2024-11-04T15:35:19.860633Z  INFO spotify_player::auth: Using cached credentials
2024-11-04T15:35:19.860648Z  INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "spotify-player", device_type: Speaker, is_group: false, initial_volume: Some(41942), has_volume_ctrl: true }
2024-11-04T15:35:19.860730Z  INFO librespot_playback::mixer::softmixer: Mixing with softvol and volume control: Log(60.0)    
2024-11-04T15:35:19.860789Z  INFO spotify_player::streaming: Initializing a new integrated player with device_id=4d0c616a-644d-43ca-99c7-2450085454d8
2024-11-04T15:35:19.860896Z  INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol
2024-11-04T15:35:19.861010Z  INFO librespot_playback::convert: Converting with ditherer: tpdf    
2024-11-04T15:35:19.861123Z  INFO librespot_playback::audio_backend::rodio: Using Rodio sink with format S16 and cpal host: CoreAudio    
2024-11-04T15:35:19.921549Z  INFO librespot_playback::audio_backend::rodio: Using audio device: MacBook Pro Speakers    
2024-11-04T15:35:20.281013Z  INFO librespot_core::session: Connecting to AP "ap-gue1.spotify.com:4070"    
2024-11-04T15:35:21.727693Z  INFO librespot_core::session: Authenticated as '31bewedqaetpovv3yqnw44jtphsy' !    
2024-11-04T15:35:21.728739Z  INFO librespot_core::session: Country: "CA"    
2024-11-04T15:35:21.728989Z  INFO spotify_player::streaming: New streaming connection has been established!
2024-11-04T15:35:21.729036Z  INFO spotify_player::client: Used a new session for Spotify client.
2024-11-04T15:35:21.729162Z  INFO spotify_player::token: Getting a new authentication token...
2
<!-- gh-comment-id:2483380005 --> @aome510 commented on GitHub (Nov 18, 2024): Hi, I think you mistook Spotify device with the actual physical device. "Device" here refers to an **active Spotify client**, which can be `spotify_player`'s integrated client, Spotify Desktop app, or Spotify mobile app on your phone. One thing I realized from your log is that there is no integrated client initialized on startup. Are you sure you run the application with the right set of features? Based on the log, I'm pretty sure that the `streaming` feature is not enabled. There should be lines as follows in the log at the beginning, which you can compare to yours to see the differences: ``` 2024-11-04T15:35:19.854566Z INFO spotify_player::state::data: Successfully loaded SavedTracks data! 2024-11-04T15:35:19.860633Z INFO spotify_player::auth: Using cached credentials 2024-11-04T15:35:19.860648Z INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "spotify-player", device_type: Speaker, is_group: false, initial_volume: Some(41942), has_volume_ctrl: true } 2024-11-04T15:35:19.860730Z INFO librespot_playback::mixer::softmixer: Mixing with softvol and volume control: Log(60.0) 2024-11-04T15:35:19.860789Z INFO spotify_player::streaming: Initializing a new integrated player with device_id=4d0c616a-644d-43ca-99c7-2450085454d8 2024-11-04T15:35:19.860896Z INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol 2024-11-04T15:35:19.861010Z INFO librespot_playback::convert: Converting with ditherer: tpdf 2024-11-04T15:35:19.861123Z INFO librespot_playback::audio_backend::rodio: Using Rodio sink with format S16 and cpal host: CoreAudio 2024-11-04T15:35:19.921549Z INFO librespot_playback::audio_backend::rodio: Using audio device: MacBook Pro Speakers 2024-11-04T15:35:20.281013Z INFO librespot_core::session: Connecting to AP "ap-gue1.spotify.com:4070" 2024-11-04T15:35:21.727693Z INFO librespot_core::session: Authenticated as '31bewedqaetpovv3yqnw44jtphsy' ! 2024-11-04T15:35:21.728739Z INFO librespot_core::session: Country: "CA" 2024-11-04T15:35:21.728989Z INFO spotify_player::streaming: New streaming connection has been established! 2024-11-04T15:35:21.729036Z INFO spotify_player::client: Used a new session for Spotify client. 2024-11-04T15:35:21.729162Z INFO spotify_player::token: Getting a new authentication token... 2 ```
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#354
No description provided.