mirror of
https://github.com/advplyr/audiobookshelf-app.git
synced 2026-07-25 22:18:38 +02:00
When Siri's notification announcement stops, Audiobookshelf resumes from a point further in the past than where Siri interrupted #399
Reference in New Issue
Block a user
Originally created by @Piste on GitHub (Jan 11, 2023).
Steps to reproduce
Expected behaviour
Environment data
Audiobookshelf Version: 2.2.12 (docker)
iOS Issue
iOS Version: 0.9.60-beta
iPhone model: 14 Pro
@Piste commented on GitHub (Jan 11, 2023):
This could be related to #191 but my playback resumed, just not in the right spot.
@advplyr commented on GitHub (Jan 11, 2023):
How far back does it jump?
There is some logic that automatically rewinds a bit after a pause. We can tweak that logic but I want to make sure that is what you are experiencing first.
@Piste commented on GitHub (Jan 13, 2023):
The one time this happened to me, it jumped back to the point I had hit "play".
However, I received a Siri announcement recently and the playback pause and resume handled it perfectly.
I'll keep an hear out. This might have been a one-off.
@Piste commented on GitHub (Jan 20, 2023):
This has been happening more frequently. For example, a multiparty Signal (messaging) channel got busy and people were replying to each other while I was listening to a book and the playback would always resume to that same point in the past after Siri was done announcing. That resume point was maybe 15-30 seconds in the past(?) this means that every time Siri interrupted playback, I could expect the same part of the book again.
@benonymity commented on GitHub (Feb 1, 2023):
Are you still experiencing this issue on 0.9.61-beta? While the play/pause takes a second or so, it resumes at the proper place.
@mym0T commented on GitHub (Feb 2, 2023):
I have not experienced this issue since updating to 0.9.61
This was happening to me fairly often on 0.9.60 and earlier. It seemed to be caused by or related to skipping backward or forward in the book via the buttons in the player.
When it happened to me, the current time/progress would stop advancing, so I would check that the time was still changing after anytime I used the skip buttons. If it wasn't, I could usually get it working again by skipping backwards and forwards a few more times.
@advplyr commented on GitHub (Feb 12, 2023):
Thanks, we can re-open this if it continues to be an issue on the latest release.