mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #907] No playback found #548
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#548
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 @Horymz4 on GitHub (Jan 4, 2026).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/907
Hey idk if I'm doing something wrong but I cannot control or see any of my playlists or tracks, it just says No playback found at the top. I can however control the app through another device like a web player. I can also see the devices with SwitchDevices cmd, but clicking them doesnt work.
thx for help
@iam-vasanth commented on GitHub (Jan 4, 2026):
It's an on-going issue with the pre-built binary of spotify-player because of some dependency they use. The issue has been resolved in upstream git version. Clone the upstream git version and compile it.
@Horymz4 commented on GitHub (Jan 4, 2026):
Thank you every much.
@KingKnecht commented on GitHub (Jan 21, 2026):
I cloned the repo and build successfully with all features enabled. Still no devices.
@iam-vasanth what do you mean with "Clone the upstream git version"? Is that different to clone master?
@Horymz4 commented on GitHub (Jan 21, 2026):
Are you typing "cargo build"? becouse if you type "cargo install" it wont be the latest git version
@KingKnecht commented on GitHub (Jan 21, 2026):
yes
cargo build --all-featuresResult:
@iam-vasanth commented on GitHub (Jan 21, 2026):
Hi @KingKnecht , Make sure you have defined client_id in app.toml file.
Also, Which OS are you on? Because i use Nixos and it did not work for me. I have tried all the solutions and gave up. I cloned it from main/master branch and built it on a arch distro box container. It worked there for me. It was weird why it did not work on Nixos though when i did the same.
Here is the cmd i used to build :
cargo install --git https://github.com/aome510/spotify-player.git --features image@KingKnecht commented on GitHub (Jan 21, 2026):
I'm on
CachyOS x86_64
Linux 6.18.5-2-cachyos
@KingKnecht commented on GitHub (Jan 21, 2026):
@iam-vasanth are there any log files to check?
@iam-vasanth commented on GitHub (Jan 21, 2026):
Not sure then, I wish i could try and let you know but i deleted my spotify app from my dev dashboard while testing this issue and i can't create a new app right now because spotify has stopped new app registrations temporarily. Im just using the default spotify client now. Hope someone who knows better than me will help you!
@KingKnecht commented on GitHub (Jan 21, 2026):
@iam-vasanth I think I misunderstand the application. "Device" has probably nothing to do with audio device. It's a Spotify device, I think. What ever that is ^^
I thought it's just like the spotify-launcher (looks like the Spotify app on Windows) but without fancy graphics. But meanwhile I think it's not that easy... or is it/should it be?
@iam-vasanth commented on GitHub (Jan 21, 2026):
Yes, Device in the sense it meant spotify connect devices. That is the reason if asked if you have followed the spotify connect setup process by adding
client_idtoapp.tomlconfig file. If already have gone through the setup. It's the application or the version issue.@iam-vasanth commented on GitHub (Jan 21, 2026):
If you're still facing the issue, I would recommend opening a new issue thread or look for a similar issue thread which is in open status because this is closed and idt anyone other than us will go through this issue thread.