mirror of
https://github.com/advplyr/audiobookshelf-app.git
synced 2026-07-25 22:18:38 +02:00
[Bug]: Mobile app ignores external progress when playing #936
Assignees
adam (Adam Melkus)
Clear assignees
adam (Adam Melkus)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf-app#936
Reference in New Issue
Block a user
Originally created by @KRSogaard on GitHub (Apr 2, 2024).
Describe the issue
When moving from Web to Mobile decide, the mobile deceive will show the correct progress, but as soon as i click pay it will reset.
This happens to me almost every time i listen to an audiobook and switch device, example last night i was listening to a book up until "2:38:00" on my mobile phone, during the day today i have been listening via the web up until "5:07:02".
When i open my mobile app, it shows the correct time "5:07:02" as the current progress, but as soon as i click pay on the mobile device it resets to "2:38:00" and continues from there. To make the problem worse it "reports" this to set server as the current progress, overwriting my actual progress.
Steps to reproduce the issue
Audiobookshelf version
v2.8.1
How are you running audiobookshelf?
Docker, Android App
@nichwall commented on GitHub (Apr 2, 2024):
Did you close the mobile app completely while listening on the web app?
@advplyr commented on GitHub (Apr 2, 2024):
Please provide both the server version you have installed and the android app version you have installed. It is also helpful if you provide the android OS version you are using.
Also, it is important to add if you are experiencing this with downloaded books or streaming books or both.
@KRSogaard commented on GitHub (Apr 3, 2024):
I was able to catch it on video today: https://www.youtube.com/shorts/o7nfUfMNsHM
I have been listening on my laptop, and wanted to switch to my mobile. I stopped the playback on the web browser at 7:36:40, i then waited roughly 2 min to make sure the server has been updated.
I then started the screen recording above, You will see that is set the current progress to 7:36:08 (a bit off the 7:36:40 on the web browser but this is ok), i then click the play button and i feel the phone vibrate twice and i see the progress jump back to 6:23:00 the progress i had when i stopped listening on my phone last time.
The android app is the latest from the Google Play store, version 0.9.73-beta, and i am streaming the book.
@nichwall commented on GitHub (Apr 3, 2024):
Did you completely close the mobile app while you were listening on the computer? The video looks like the player was not closed (this can be done by either closing the player or force closing the app)
If so, this is the same behavior as https://github.com/advplyr/audiobookshelf-app/issues/1146?
@advplyr commented on GitHub (Apr 3, 2024):
In this case since the player has correctly synced the progress from the web in real-time using websockets that should not have jumped back like that. I'll look into it
@KRSogaard commented on GitHub (Apr 3, 2024):
@nichwall no i did not clock the app fully, it was running in the background. However i have seen it do the same thing when i force close the app first. Also it is clear it got the update from the server as it is a the right place before i push play, so i don't think that is the issue.
@JReming85 commented on GitHub (May 15, 2024):
I can confirm, if you close the app (force close) and reopen it will continue from where the web app is currently at.
History seems to only log the mobile app's progress, as I cant see the option on the browser version but would be great if it could sync both.
Not the biggest of issues, but an annoying QoL request/fix
@Inevitable commented on GitHub (Aug 12, 2024):
Confirming that I also see this behavior; essentially I MUST force stop the Android app, or any progress state on the server is overwritten. This is quite a big annoyance as I move between the two players (web and mobile app) several times a day, and a server-authoritative progress sync was one of the top reasons I was interested in running this service!
@giejay commented on GitHub (Jan 10, 2026):
I'm using https://github.com/cporcellijr/abs-kosync-bridge/tree/main to sync progress from my KoReader to ABS and vice versa. I'm also experiencing this issue on my Android device (latest version). If I don't force close the app, the push from abs-kosync-bridge to ABS is ignored and not visible in the History. When I force close and re-open, I see the "Sync" item in the history view and the progress is updated correctly.
I will try to build the Android app using the PR from https://github.com/advplyr/audiobookshelf-app/pull/1771 and try to get some more logs. I feel like it should just do another fetch from the server in the onResume() but that might be simplifying it a bit;)
@giejay commented on GitHub (Jan 10, 2026):
I have some more information. I'm using the latest develop debug version. It indeed seems to be related to the websocket connection breaking and in the progress of reconnecting, it doesn't fetch the latest state from the server.
Happy scenario, app is opened, I'm changing progress in the web interface:
Progress is updated perfectly. But now, the screen of the phone turns off, and after some time:
the websocket disconnects and doesnt properly reconnect until after I open the screen again:
But the progress is still at where it was, locally, after the screen turned off. I see this call is being made:
But shouldn't it also fetch the latest state from the server, like it's (assumption) doing on boot-up of the app? After I force close the app and open it again, progress is where it should be.
@giejay commented on GitHub (Jan 10, 2026):
I tried my best in fixing it: https://github.com/advplyr/audiobookshelf-app/pull/1777. For me it works at least but I'm hoping I did not break anything else now:)