mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #1438] Transfer playback fails to find track #651
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#651
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 @FabioGNR on GitHub (Jan 11, 2025).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1438
Description
When I use the Spotify desktop application (Linux) to transfer playback to the librespot device, librespot fails to find a track
"ERROR librespot_connect::spirc] ContextError: Invalid state { track uri contains invalid characters }" and does not resume playback.
Version
v0.6.0-15-g7003e98How to reproduce
librespot(without args)Log
Host (what you are running
librespoton):Additional context
Also tried to transfer from Android app, with same result.
Logs show a song played from "Liked Songs", but tried with a playlist and album and got same result.
@FabioGNR commented on GitHub (Jan 11, 2025):
In the
playback.current_trackfield ofTransferStateI only seeuidfilled in,uriis None.I have not yet been able to find a reference to the track uri or index in the Liked Songs.
However, the
metadatafield ofContextTrackdoes have the correct title of the song.@FabioGNR commented on GitHub (Jan 11, 2025):
I now see it should be able to get the track based on gid, but it appears because "uri" is an empty string instead of None, it does not reach that branch. I'll try to see if handling empty uri string fixes this.
@photovoltex commented on GitHub (Jan 11, 2025):
Seems like you are probably on the right track already. Thanks for the deeper investigation on the issue^^