mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: Web Player starts playing triggered by the Android app, gets out of sync #2976
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#2976
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LastElf on GitHub (Aug 30, 2025).
What happened?
I've had this happen a couple of times now but can't work out the trigger. I was playing a book via Firefox, paused it and left the tab (and player frame) open. Some time later in another room I resumed it on my phone via the app and unknowingly to me, my PC started playing as well. I paused on my phone and could still hear it coming from my PC. This threw the two players out of sync with each other and then the most recent one to be stopped is the one that recorded where I was up to.
What did you expect to happen?
The app to not start my PC playing
Steps to reproduce the issue
Can only reproduce it on accident at the moment. I suspect there's a websocket thing going on with leaving the player frame open, but the fact that it won't sync every play/pause makes it hard to repro. I will note the book is downloaded to my phone, and today when it happened both PC, phone and server were all on the same network. I have been able to have my PC play while I was leaving the house but I can't remember if I was on the edge of my wifi when I hit play that time.
Audiobookshelf version
2.29.0
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
No response
@Vito0912 commented on GitHub (Aug 30, 2025):
Do you have an extension that triggers auto playing on syncing?
The progress gets synced if you leave the player open, but it should not automatically play.
Can you try to reproduce this on a stock browser?
(Note that leaving the player open in general is a very bad idea, because it can revert progress if the websocket is broken and you close it while it's in an older state)
@LastElf commented on GitHub (Aug 31, 2025):
No extensions, Firefox pretty much only has adblock, password manager and a few context specific utilities. ABS is as vanilla install as you can get.
Like I said, I couldn't quite work out what triggered it, it's only happened 3 times in the last few months but I don't listen on my PC often.
If the socket stays open the entire time the player is loaded that could be part of it, I expected there to be some kind of timeout after 5 minutes where it would unload the socket but leave the player open, and then hitting play would let it spend a few seconds re-handshaking and then catch back up (Similar to Plex or Youtube). If that's all I can try and remember to close the player too and that should mitigate the issue, possibly just a bad assumption on my part.
@Vito0912 commented on GitHub (Aug 31, 2025):
As said ABS should never hit play on its own. I don't even think there is functionality added for it.
This sounds more of a bug of Firefox then (although I use it too and never had such experience).
The socket does not unload as long there is a internet connection (even if the player is paused). Maybe it has something to do with Firefox unloading the whole page and reloading the page which maybe then auto resumes if the page is loaded again
@advplyr commented on GitHub (Sep 3, 2025):
Maybe your browser is sending a media session event? The audio player uses the media session API which can connect to keyboards and things like that. I don't know all the uses but that is the only thing I can think of.
https://developer.mozilla.org/en-US/docs/Web/API/MediaSession/setActionHandler
@Gallardo26 commented on GitHub (Sep 24, 2025):
I experienced similar issue on my Chrome browser. I get warning on my phone that the audiobook is also playing on another device (which is my desktop chrome browser). It always does this, and only way is to close my chrome ABS tab if i want to play on my phone. Using unraid ABS docker from the Community Appstore.