We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With the Spotify service, Tizonia repeats the first track of the internally generated playback queue.
It seems to occur with most of the Spotify command-line options, and only with Spotify.
Expected behavior:
Correct, sequential playback of the items in the play queue.
Actual behaviour:
As stated in the description.
Reproduces how often: Always, under the conditions stated (It seems to occur with most of the Spotify command-line options, and only with Spotify).
It occurs in 0.17.0, probably in earlier versions as well.
All of them.
The text was updated successfully, but these errors were encountered:
This issue has been reported in Reddit by user https://www.reddit.com/user/Audinot:
Sorry, something went wrong.
libtizspotify: avoid calling 'next_uri' or 'prev_uri' if the proxy pl…
b20faa2
…ayback queue is empty (#560 and #569)
Fixed in the 'develop' branch. Will be merged to master and closed before the next release.
f7a50b8
juanrubio
No branches or pull requests
Description
With the Spotify service, Tizonia repeats the first track of the internally generated playback queue.
Steps to Reproduce
It seems to occur with most of the Spotify command-line options, and only with Spotify.
Expected behavior:
Correct, sequential playback of the items in the play queue.
Actual behaviour:
As stated in the description.
Reproduces how often:
Always, under the conditions stated (It seems to occur with most of the Spotify command-line options, and only with Spotify).
Versions
It occurs in 0.17.0, probably in earlier versions as well.
Installation Method Used
All of them.
The text was updated successfully, but these errors were encountered: