You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discovered some odd behaviours, please check.
Automatic update of Up next needs to be enabled for this.
Message "Up next has been updated by" does not appear:
Create a new playlist add several episodes
Start playing an episode so Up next will be update (message "Up next has been updated") appears
Go to Up next and e.g. remove an episode (message "will not be updated anymore" appears)
Go back to your created playlist and start playing again
Now: No message appears that this Up next has been from this playlist, but it has been updated
If you play a single episode from a podcast directly, the message appears
The message also appears when you clear Up next manually and start playing from you playlist
Update (sync) symbol does not change:
Make sure Up next is update from a playlist
Remove an episode via swipe or long press -> message "will not be updated anymore" appears
I would expect that sync symbol changes like when reordering the episodes in the list.
Playing a single episode sometimes gets appended to Up next and sometimes not:
I cannot reproduce it, but sometimes an episode will be appended to Up next when start playing a single episode from podcast and sometimes not (then only the currently played episode is in Up next).
The text was updated successfully, but these errors were encountered:
Discovered some odd behaviours, please check.
Automatic update of Up next needs to be enabled for this.
Message "Up next has been updated by" does not appear:
Update (sync) symbol does not change:
Playing a single episode sometimes gets appended to Up next and sometimes not:
I cannot reproduce it, but sometimes an episode will be appended to Up next when start playing a single episode from podcast and sometimes not (then only the currently played episode is in Up next).
The text was updated successfully, but these errors were encountered: