Roku client appears to NOT update NFO file after video finishes playing through to the very end

[thecodygriffin]

Software Versions

• Jellyfin Server Version: 10.9.7
• Roku Client Version: 2.0.7

Describe the bug

Upon allowing a video to play through to the very end, the Roku client appears to NOT prompt the update of the corresponding NFO file.

To be very specific, "watched" is NOT updating from "false" to "true" in the corresponding NFO file.

Prerequisites To Reproduce

1. Navigate to the Libraries > Libraries section of the JellyFin server from the Dashboard in the main navigation
2. Select the "Manage library" option in the kebab menu for the testing library
3. Select the "Nfo" checkbox in the "Metadata savers" section for the testing library
4. Select "OK" to save the setting
5. Navigate to the Libraries > NFO Settings section of the JellyFin server in the main navigation menu
6. Select the the user to be used for testing in the "Save user watch data to NFO files for" field
7. Select "Save" to save the setting

How To Reproduce

1. Open the JellyFin Roku client
2. Ensure you are logged in with the same user selected in Step 6 of the "Prerequisites To Reproduce" section
3. Navigate to the library selected in Step 2 of the "Prerequisites To Reproduce" section
4. Select any video that has not yet been watched
5. Watch the video through to the very end when the stream closes and returns you to the library

Expected behavior

The NFO file is updated including "playcount" and "watched" among others when applicable

Logs

There are no [ERR] messages in the logs for my testing time range. There was an instance of the following [WRN] message, but it does not appear to correlate with the behavior experienced.

[2024-07-03 10:52:25.892 -04:00] [WRN] WS "10.16.8.1" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."

Connection Information

• Is server local or remote? LOCAL
• Is server connection HTTP or HTTPS? HTTP

Additional context

If the video is exited by the user prior to conclusion, the NFO file is updated as expected whether that be the "watched", "playcount","lastplayed", or "resume" values.

Furthermore, the behavior is NOT reproducible from the Android or Web clients.

[roidy]

Maybe related to the following issue:- #1567

The app handles the stopped state which happens when the user ends a file by pressing back on the remote but fails to handle the finished state which is fired when the media naturally stops at the end with no user interaction.