mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 01:15:55 +03:00
[GH-ISSUE #864] Tracks skipping without playing #521
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#521
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 @arch-btw on GitHub (Nov 6, 2025).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/864
Describe the bug
Tracks are skipping without playing
To Reproduce
When I play a track that isn't cached then it won't play
Expected behaviour
For it to play music
Log and backtrace
Environment
Additional context
Apologies if it's just my setup, everything was playing fine yesterday though.
@kubiokyay135 commented on GitHub (Nov 6, 2025):
Hello there good sir,
I actually experienced this bug a few days ago and found a work-around. From my understanding this isn't an issue with spotify-player, but instead is a bug in librespot which affects a lot of custom spotify apps. Originally ran into this with Music Assistant linked to Home Assistant earlier this year.
To fix (as a workaround), edit your hosts file on your computer and add "0.0.0.0 apresolve.spotify.com" to block the domain. This forces spotify to use an alternate cdn backend that still works properly.
@Mega2223 commented on GitHub (Nov 6, 2025):
Fellow Arch User here having the exact same problem, and everything was fine yesterday too. Did you by any chance make a system update recently?
@kubiokyay135 commented on GitHub (Nov 6, 2025):
I apologize, I guess I spoke too soon. When I first installed the app a few days ago I was getting this issue, and fixed it with the hosts file change I mentioned above. However, as of this morning it looks like that isn't working either and I'm now experiencing this bug again. Checked my logs and I'm getting the exact same errors you're getting.
Something had to have changed on Spotify's end. No changes were made on my system between yesterday and this morning, and it was working about 10hrs ago.
@arch-btw commented on GitHub (Nov 6, 2025):
@kubiokyay135 no problem at all 👍 , and thank you for the fast reply! Unfortunately, it didn't work for me either, but I do recall that being a fix earlier this year indeed.
@Mega2223 good catch! I did do a full update earlier today. Maybe something broke along those lines.
@lucasadelino commented on GitHub (Nov 6, 2025):
Also broken for me after running a system update on Arch
@afxfinn commented on GitHub (Nov 6, 2025):
Hi, same issue arising on my end as well, also running Arch + latest version of this, but did not do a system update recently.
Stopped working about 4 hours before posting this comment, worked fine earlier today.
@Simplicitie commented on GitHub (Nov 6, 2025):
Happens on MacOS too.. I was using it this morning.. paused to join a short meeting and it was broken by the time I got back. Same errors in the log file.
@trentcowden commented on GitHub (Nov 6, 2025):
Happening for me on MacOS as well! I can't play anything.
@OneTrueJASH commented on GitHub (Nov 6, 2025):
https://github.com/librespot-org/librespot/pull/1622
@aome510 commented on GitHub (Nov 6, 2025):
hi folks, just chime in this thread cause I haven't touched the project for a while. Can someone ping me once librespot releases new version with the fix so that I publish a new release?
@OneTrueJASH commented on GitHub (Nov 6, 2025):
I've tested locally with the proposed librespot fix and can confirm it resolves the playback issue.
To get spotify-player working with PR #1622, I had to make a couple of code changes to accommodate the new librespot API. One of the commits since the last librespot release refactors how Spotify URIs are handled, replacing
SpotifyIdwith a newSpotifyUrienum.Changes required:
spotify_player/src/streaming.rs- Updatedspotify_id_to_playable_id()function:spotify_id::SpotifyIdtoSpotifyUrimatch id.item_typewith pattern matching onSpotifyUrienum variants (SpotifyUri::Track { .. },SpotifyUri::Episode { .. })spotify_player/src/client/mod.rs- Updatedlyrics()method:SpotifyId::from_uri()toSpotifyUri::from_uri()SpotifyIdfrom theSpotifyUri::Track { id }variantWith these changes, spotify-player builds successfully and can now play tracks without the "Track should be available, but no alternatives found" errors.
Once librespot PR #1622 is merged, spotify-player will need to adopt these API changes to remain compatible with the fix.
@aome510 commented on GitHub (Nov 6, 2025):
Thanks @OneTrueJASH for looking into this! If possible, once librespot releases a new version, can you put up a PR here as well?
@OneTrueJASH commented on GitHub (Nov 6, 2025):
@aome510 for sure. Glad to help out. I'll let you know when the PR is ready for review.
@richardhapb commented on GitHub (Nov 7, 2025):
You can use this patch while this is solved.
https://github.com/richardhapb/spotify-player/tree/patch
@Douglas019BR commented on GitHub (Nov 7, 2025):
I tried this patch, but doesnt work to me, i got the same error described on this issue
@richardhapb commented on GitHub (Nov 7, 2025):
Can you check if you are using the proper executable please?
You can also test cleaning the build with Cargo beforehand.
@trentcowden commented on GitHub (Nov 7, 2025):
I also tried the patch but it didn't fix the issue for me!
I ran:
@richardhapb commented on GitHub (Nov 7, 2025):
Do this instead.
@OneTrueJASH commented on GitHub (Nov 7, 2025):
Update on librespot release of fixed version:
https://github.com/librespot-org/librespot/issues/1623#issuecomment-3503714872
@trentcowden commented on GitHub (Nov 7, 2025):
That did it! Thank you much!
@mrghosti3 commented on GitHub (Nov 7, 2025):
It's now merged in librespot dev branch
@OneTrueJASH commented on GitHub (Nov 7, 2025):
Just waiting on a release
@Alexander3a commented on GitHub (Nov 8, 2025):
here changed to use the official repo librespot (spotify-player changes from richardhapb)
edit: updated the patch to the new version number
if it breaks again try replacing
branch = "dev"withrev = "d36f9f1907e8cc9d68a93f8ebc6b627b1bf7267d"in Cargo.toml@kohane27 commented on GitHub (Nov 8, 2025):
@Alexander3a Thank you so much for the step-by-step guide. I followed it and can verify that it works!
@martinprad0 commented on GitHub (Nov 10, 2025):
Is the patch for this issue already published? I tried rebuilding the cargo package with
cargo install --git https://github.com/aome510/spotify-player --forcebut the issue still persists. Just so I know if I open a new issue.@Eulenberg commented on GitHub (Nov 10, 2025):
i tryed building it like it is from souce like 10 minutes ago, issue persists, @Alexander3a patch seems no not work anymore for some reason getting the following error
@kohane27 commented on GitHub (Nov 11, 2025):
@Eulenberg You have a build issue. Is there any error when you applied the patch? You can say the patch won't work when it compiled and the player would not play any songs.
@Alexander3a commented on GitHub (Nov 11, 2025):
librespot-org has updated the patch is no longer working for the newest version
i have updated the patch to target the working rev
edit: i noticed they only updated the version number so i have also updated my patch above
lets see how long till it breaks again and i cant target dev anymore
@antoniorodr commented on GitHub (Nov 11, 2025):
Hi!
I have the same problem too, I think. The songs will not start reproducing, but the "Spotify-player" appears as a device.
I am on macOS, installed thought homebrew
@Eulenberg commented on GitHub (Nov 11, 2025):
@Alexander3a thank you sooo much !!!
@wawwior commented on GitHub (Nov 11, 2025):
librespots newest release includes #1622 now
@Eulenberg commented on GitHub (Nov 11, 2025):
@wawwior does this mean we can build a working binary from this source again without the patch provided by @Alexander3a ?
@wawwior commented on GitHub (Nov 11, 2025):
@Eulenberg no, not until this is updated to the new version, which is a process pretty much identical to the patch.
@Douglas019BR commented on GitHub (Nov 11, 2025):
@Alexander3a I created a PR with your suggestion. I tested it on my machine and it works pretty well. I really want to thank you because of this—my days are much better with spotify_player :) I created the PR just so people from this issue can get back to listening to music faster, but if you prefer, I can close my PR and wait for yours.
@martinprad0 commented on GitHub (Nov 14, 2025):
I know this is closed, because it was working yesterday. But today the problem emerged again, should I open a new issue?
@Douglas019BR commented on GitHub (Nov 14, 2025):
I just tried it and it works well. Please try uninstalling the version you had installed, update the repo, and install it again. If it still doesn't work, try to capture the error log.
@aome510 commented on GitHub (Nov 14, 2025):
yes just tried it and things seem to work well for me
@damianmr commented on GitHub (Nov 14, 2025):
Hi @aome510, is there any chance we could get a homebrew release of the latest minor
0.21.2? Homebrew is still installing0.21.1@OneTrueJASH commented on GitHub (Nov 14, 2025):
@damianmr
https://formulae.brew.sh/formula/spotify_player is showing the stable version as
0.21.2If your Homebrew keeps installing
0.21.1, you might try targeting the specific version with yourbrew installcommand@damianmr commented on GitHub (Nov 14, 2025):
Sorry, I forgot to upgrade my formulas before trying 🫣 Thanks,
0.21.2fixed the audio issue for me.