Offline listening progress is not syncing back to Audiobookshelf server

[hugorn]

Hi! First of all, thank you for creating ShelfTime. It works really well on my Galaxy Watch.

I found what appears to be a synchronization issue with offline listening progress.

Environment

• Device: Samsung Galaxy Watch 6 Classic
• Wear OS version: 8.0
• ShelfTime version: Latest in Play store
• Audiobookshelf server version: 2.36

Steps to reproduce

1. Install ShelfTime from the Google Play Store on the watch.
2. Connect it to an Audiobookshelf server.
3. Download an audiobook for offline listening.
4. Listen to part of the audiobook while offline.
5. Reconnect the watch to the internet.
6. Tap the green cloud icon to sync progress.

Expected behavior

The listening progress should be uploaded to the Audiobookshelf server and be reflected on the web interface and the Android app.

Actual behavior

After tapping the green cloud icon:

• The icon turns gray, indicating that the sync has completed.
• However, the listening progress is not updated on the server.
• The audiobook still shows 0% progress in both the Audiobookshelf web interface and the Android app.
• If I continue listening on another device, it starts from the beginning instead of the position reached on the watch.

Additional information

• Downloading the audiobook works correctly.
• Offline playback works correctly.
• The issue seems to affect only the upload of listening progress back to the server.

If there is any log or debug information I can provide, I'd be happy to help test it.

Thank you!

[hugorn]

Logs:
2026-08-04 16:48:06.051

INFO

[SocketAuthority] Socket Connected to /audiobookshelf/socket.io SDAgoKcVWJ4NYayfAAAL

2026-08-04 16:48:15.114

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:48:14.340 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:48:18.993

INFO

[SocketAuthority] Socket SDAgoKcVWJ4NYayfAAAL disconnected from client "hxxxxxxxxxxx@gmail.com" after 12942ms (Reason: transport close)

2026-08-04 16:48:19.429

INFO

[SocketAuthority] Socket Connected to /audiobookshelf/socket.io 9wTGCcadFBN7wybeAAAN

2026-08-04 16:48:21.638

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:48:14.340 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:48:24.848

INFO

[SocketAuthority] Socket 9wTGCcadFBN7wybeAAAN disconnected from client "xxxxxxxxx@gmail.com" after 5420ms (Reason: transport close)

2026-08-04 16:48:25.321

INFO

[SocketAuthority] Socket Connected to /audiobookshelf/socket.io eTGa4xVuQynVJwQXAAAP

2026-08-04 16:49:01.834

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:48:14.340 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:49:04.871

INFO

[SocketAuthority] Socket eTGa4xVuQynVJwQXAAAP disconnected from client "xxxxxxxxxxxx@gmail.com" after 39550ms (Reason: transport close)

2026-08-04 16:49:05.418

INFO

[SocketAuthority] Socket Connected to /audiobookshelf/socket.io i_Llhd20W74wzbbhAAAR

2026-08-04 16:49:34.159

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:48:14.340 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:50:19.085

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:50:18.446 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:50:43.970

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:50:43.446 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:50:47.927

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:50:43.446 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)`

[hugorn]

Log with debug.

2026-08-04 16:54:23.725

DEBUG

Set Log Level to DEBUG

2026-08-04 16:54:23.745

DEBUG

[ApiCacheManager] Array.afterUpsert: Clearing cache

2026-08-04 16:55:03.001

DEBUG

[TokenManager] User xxxxxxxxxxx@gmail.com is using an access token without an expiration

2026-08-04 16:55:03.215

DEBUG

[ApiCacheManager] mediaProgress.afterUpdate: cleared user-progress cache slices (personalized=0, recentEpisodes=0, me=0)

2026-08-04 16:55:03.216

INFO

[MediaProgress] Manually setting updatedAt to '2026-08-04 19:55:00.365 +00:00' (media item 9d49c3e0-5c6b-403e-bc44-e47cb91e0075)

2026-08-04 16:56:28.879

DEBUG

Set Log Level to DEBUG

2026-08-04 16:56:28.891

DEBUG

[ApiCacheManager] Array.afterUpsert: Clearing cache

[mkaflowski]

Thank you for the detailed report - the steps and the server logs made this much easier to track down, and there turned out to be three separate bugs behind it.

First, the app only ever sent currentTime and lastUpdate to the server. Audiobookshelf stores progress and duration exactly as the client sends them and never recalculates them, so for a book that had no progress record on the server yet, it created one with duration 0 and progress 0. Your position was actually being stored, but every Audiobookshelf client displayed it as 0%. The app now sends the duration and the progress fraction as well.

Second, for books that were never played through the server, the app had no progress object to write into and quietly discarded every update - so in some cases nothing was saved locally in the first place. That's fixed too.

Third, the reason the cloud icon turned gray without anything happening: after a successful upload the app tried to clear the "pending upload" flag, but the database write was rejected because the timestamp hadn't changed, and the icon was only updated in the UI, not in the database. That's why your log shows the same progress being uploaded over and over with an identical timestamp.

All three are fixed for the next release. Existing books that are stuck at 0% on the server should correct themselves the first time the watch syncs after updating - no need to re-download anything.

I haven't been able to test this end to end against a live server yet, so if you're still up for it, I'd really appreciate you confirming once the update is out: listen offline for a minute or two, reconnect, tap the cloud icon, and check whether the position and the percentage show up in the web UI. If anything is still off, the server log lines like the ones you posted are exactly what I need.

[BlueFeatherBoa]

@mkaflowski - not the original reporter, but came here after the loss of syncing was driving me mad ;). Installed the latest release (1.2), and I can confirm that it's properly syncing now. Also super happy that you fixed the requesting wifi issue! I'm super confused, though - when I went looking for the changes in the code, they were all super old: am I crazy?