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
doesn't report its playback once stopped. Hence, breaking the list sync plugin.
As long as Findroid reports its playback location when it stops (regardless of location when skipping), Jellyfin Server, and its respective plugins, will respond accordingly as if it were finished completely.
Tested with multiple shows and episodes. Same result.
Device
Samsung Galaxy S24 U
Android version
14
App version
v0.15.3
Jellyfin version
10.10.0
The text was updated successfully, but these errors were encountered:
Describe your issue
Whilst viewing a series and skipping to the next item using the previous item and next item buttons, the previous item isn't reported as "stopped".
Steps to reproduce
Expected behavior
Playback needs to be reported by the app when skipping, and where it stopped.
Otherwise, certain plugins may break.
In the logs, it should say something along the lines of:
Screenshots
Skipping to next episode doesn't show it being "stopped" in logs
Player
mpv
Additional context
Complete Fix for issue #340
Related to #869
Basically the same issue, only except with the next / previous media buttons
I am running Windows Version of Jellyfin Server
10.10.0
Jellyfin Android App (Skipping onto the next episode):
Runs fine, correctly reporting when it stopped and triggering the sync plugin.
However, in Findroid...
Findroid App (Skipping onto the next episode):
doesn't report its playback once stopped. Hence, breaking the list sync plugin.
As long as Findroid reports its playback location when it stops (regardless of location when skipping), Jellyfin Server, and its respective plugins, will respond accordingly as if it were finished completely.
Tested with multiple shows and episodes. Same result.
Device
Samsung Galaxy S24 U
Android version
14
App version
v0.15.3
Jellyfin version
10.10.0
The text was updated successfully, but these errors were encountered: