mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #861] Play Queue inconsistencies with Android and librespot. #434
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#434
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 @theBertrum on GitHub (Oct 7, 2021).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/861
Hello good people,
I have come over from the community at the moOde Forum to report some behaviour we have spotted when using the Spotify Android app in conjunction with librespot. The discussion relating to this can be read here: https://moodeaudio.org/forum/showthread.php?tid=4215 (some useful screenshots at post 10).
To reproduce the issue, first start playing a playlist (or album) by playing the first item in the playlist, this should start playing and then add the subsequent tracks into the queue as "next from".
Now connect the session to librespot (in our case via moOde) and browse to the play queue using the Android app, you will find all the "next from" items are inert.
Connect to the same session using a different Spotify client (the Spotify Web Player for example) and browse to the play queue, those same "next from" items can be interacted with.
Finally disconnect from librespot, or connect to another connect device and notice that the items are no longer inert even on the Android app.
@roderickvd commented on GitHub (Oct 7, 2021):
I can confirm this. In part #701 is the same issue. I'm not sure we can get this to work under the current Spotify API, so I'm tagging this as work to be done under the
new-apiefforts.@theBertrum commented on GitHub (Oct 7, 2021):
Thanks for looking, I thought #701 had a similar feel. I'll report back on the moOde forum and we shall wait patiently.