Rigellute / spotify-tui

Spotify for the terminal written in Rust 🚀
MIT License
17.34k stars 518 forks source link

macOS + home-manager: no devices found #653

Open rpearce opened 3 years ago

rpearce commented 3 years ago
image image

Hi, thank you for this project! Amazing.

I'm using macOS with nix+home-manager, and I've got everything running smoothly and have Spotify Premium, but when I try to play a song, it can't figure out what device to use. I'm on a MacBook Pro.

Here's my client.yml:

---
client_id: ...
client_secret: ...
device_id: ~
port: 8888

This happens even if I have the Spotify app running, as seemed to be suggested here: https://github.com/Rigellute/spotify-tui/issues/310. I have not been able to get spotifyd running on macOS with homebrew.

Thanks for your help!

andersfylling commented 3 years ago

Exactly the same issue. I'm on arch linux. Though I am not running a the official spotify application on my computer (I assumed spotifyd was a replacement from their README).

schwittlick commented 3 years ago

same issue.. it only works when the spotify app is running in parallel :/

andersfylling commented 3 years ago

If the spotifyd is running in the background, the music has to be started from an official spotify client via Spotify Connect for me. I had some serious issue getting spotifyd working in the first place.

Rigellute commented 3 years ago

Hi! This sounds like an issue with spotifyd. The device list in spotify-tui is the result of an API call to Spotify. Sounds like spotifyd is not discoverable for some reason?

andersfylling commented 3 years ago

Yeah I believe so as well, seems like it can't "discover itself", until "triggered" by another device through Spotify Connect. If that makes sense.

Spotifyd is able to see other spotify devices/instances, just not itself.

codygman commented 3 years ago

When I get this issue just restaring spotifyd with systemctl --user restart spotifyd.service fixes the issue.

codygman commented 3 years ago

https://github.com/Spotifyd/spotifyd/pull/596

llagerlof commented 3 years ago

Same problem here. Running on Windows 8.1 x64.