Originally created by @mdeeter on GitHub (Dec 7, 2023).
Steps to reproduce
Listen to book (it's one I've downloaded)
Pause book (typically done from lock screen, not sure if it matters)
Hours later, open the app
The last book will resume playing before the UI is finished loading
Expected behaviour
Preferred behavior: The book doesn't automatically start playing (or if some users want it to, make it configurable in the app settings to 'autoplay when opened'.
At the very least, I'd prefer if the book didn't start playing before the UI was loaded... it's playing before the player is even visible... so I have to wait for several seconds for the player UI to show up in order to pause the book.
Actual behaviour
Tell us what happens
Environment data
Audiobookshelf Version: 2.5.0
Android App?
iOS App? - version 0.9.68-beta
iOS Issue
iOS Version: 17.1.2
iPhone model: iPhone 12 Pro
Originally created by @mdeeter on GitHub (Dec 7, 2023).
### Steps to reproduce
1. Listen to book (it's one I've downloaded)
2. Pause book (typically done from lock screen, not sure if it matters)
3. Hours later, open the app
4. The last book will resume playing before the UI is finished loading
### Expected behaviour
- Preferred behavior: The book doesn't automatically start playing (or if some users want it to, make it configurable in the app settings to 'autoplay when opened'.
- At the very least, I'd prefer if the book didn't start playing before the UI was loaded... it's playing before the player is even visible... so I have to wait for several seconds for the player UI to show up in order to pause the book.
### Actual behaviour
- Tell us what happens
### Environment data
Audiobookshelf Version: 2.5.0
- [ ] Android App?
- [x] iOS App? - version 0.9.68-beta
#### iOS Issue
iOS Version: 17.1.2
iPhone model: iPhone 12 Pro
adam
added the bug label 2026-04-24 23:37:58 +02:00
I'm not able to reproduce this. What version of the iOS app are you using?
Is this happening every time for you? Are you leaving the app open in the background or closing it?
@advplyr commented on GitHub (Dec 8, 2023):
I'm not able to reproduce this. What version of the iOS app are you using?
Is this happening every time for you? Are you leaving the app open in the background or closing it?
app version 0.9.68-beta (updated in og description)
I typically always switch apps (leaving apps in the bg)... until something doesn't seem to be working, then I'll hard-close the app and re-open it.
It's happened several times in the past week, but it doesn't seem to happen all of the time... often enough to be a little annoying :)
@mdeeter commented on GitHub (Dec 9, 2023):
app version `0.9.68-beta` (updated in og description)
I typically always switch apps (leaving apps in the bg)... until something doesn't seem to be working, then I'll hard-close the app and re-open it.
It's happened several times in the past week, but it doesn't seem to happen all of the time... often enough to be a little annoying :)
I put in my airpods... Unlocked my phone... Opened the app...
The book started playing immediately... Here's the ui
Then I try tapping on the book... But it won't open until the ui finishes loading...
Then the book opens (it's still playing) and there's no player UI showing...
I click play button and it pauses the book and it shows the player UI at the bottom...
@mdeeter commented on GitHub (Dec 9, 2023):
Just happened again...
I put in my airpods... Unlocked my phone... Opened the app...
The book started playing immediately... Here's the ui

Then I try tapping on the book... But it won't open until the ui finishes loading...

Then the book opens (it's still playing) and there's no player UI showing...

I click play button and it pauses the book and it shows the player UI at the bottom...

I experienced this same issue. Here are some additional details in case it is helpful in recreating:
I was listening to a book on my iPhone in the car via Bluetooth.
I then switched the car to play a different audio source (though I don't think I explicitly paused Audiobookshelf)
I then was listening on my phone to the same book via headphones.
I then paused the book in my phone.
I then listened to the book on my iPad via headphones.
I paused the iPad.
Both devices were put down for several hours, but the app was not killed on either device.
When I picked up the phone several hours later, this issue popped up.
The immediately-start-playing issue doesn't bother me too much (I would hate to have a fix for this prevent being able to get in and out of a car and continue listening without a bunch of button presses), but I experienced a secondary issue where the controls were not visible while the book was playing. Possibly the same as OP's "before the UI is finished loading."
P.S. I meant to mention that major kudos are deserved fro the developers of this app. This is one of the best if not the best open source iOS apps I've experienced. It looks beautiful, runs smoothly, and does what it's supposed to. This is the one bug that I've found so far.
@dathbe commented on GitHub (Dec 20, 2023):
I experienced this same issue. Here are some additional details in case it is helpful in recreating:
I was listening to a book on my iPhone in the car via Bluetooth.
I then switched the car to play a different audio source (though I don't think I explicitly paused Audiobookshelf)
I then was listening on my phone to the same book via headphones.
I then paused the book in my phone.
I then listened to the book on my iPad via headphones.
I paused the iPad.
Both devices were put down for several hours, but the app was not killed on either device.
When I picked up the phone several hours later, this issue popped up.
The immediately-start-playing issue doesn't bother me too much (I would hate to have a fix for this prevent being able to get in and out of a car and continue listening without a bunch of button presses), but I experienced a secondary issue where the controls were not visible while the book was playing. Possibly the same as OP's "before the UI is finished loading."
P.S. I meant to mention that major kudos are deserved fro the developers of this app. This is one of the best if not the best open source iOS apps I've experienced. It looks beautiful, runs smoothly, and does what it's supposed to. This is the one bug that I've found so far.
I also have the same issue, it used to happen before but seems to got fixed. But now it's back.
Also not a big issue, i usually just press play again and it continues with the controls.
@RealWalts commented on GitHub (Dec 22, 2023):
I also have the same issue, it used to happen before but seems to got fixed. But now it's back.
Also not a big issue, i usually just press play again and it continues with the controls.
This happens whether the book is downloaded or streaming. The streaming one is way more confusing because it starts playing the audio even before the server connects.
When I go to the book that's playing it shows as if it isn't playing.
This is also happening on the macOS client which seems to be the iOS app running on Mac. It randomly starts playing there and I can't get the play controls to come up so I have to quit the app.
I just updated the server app so I'll test it this week and report back.
@livineasy629 commented on GitHub (Dec 27, 2023):
This happens whether the book is downloaded or streaming. The streaming one is way more confusing because it starts playing the audio even before the server connects.
When I go to the book that's playing it shows as if it isn't playing.
This is also happening on the macOS client which seems to be the iOS app running on Mac. It randomly starts playing there and I can't get the play controls to come up so I have to quit the app.
I just updated the server app so I'll test it this week and report back.
Still present on the latest server version and updated iOS app. It will even continue playing a file that isn't downloaded while the server is disconnected.
@livineasy629 commented on GitHub (Jan 3, 2024):
Still present on the latest server version and updated iOS app. It will even continue playing a file that isn't downloaded while the server is disconnected.
It will even continue playing a file that isn't downloaded while the server is disconnected.
This isn't too surprising. Presumably the app caches some duration while it's streaming. Would be interesting to know how long it will play when this happens.
@dathbe commented on GitHub (Jan 4, 2024):
> It will even continue playing a file that isn't downloaded while the server is disconnected.
This isn't too surprising. Presumably the app caches some duration while it's streaming. Would be interesting to know how long it will play when this happens.
It will even continue playing a file that isn't downloaded while the server is disconnected.
This isn't too surprising. Presumably the app caches some duration while it's streaming. Would be interesting to know how long it will play when this happens.
In a recent play, I just left the house and left my wifi, I opened my app in the car and got about 3-5 min away when it stopped and I noticed it wasn't connected to my server. I killed the app and reconnected and it played fine.
I agree that it seems that the app is automatically playing from the cache. I think I'd prefer it if it wouldn't autoplay when I open the app.
@mdeeter commented on GitHub (Feb 6, 2024):
> > It will even continue playing a file that isn't downloaded while the server is disconnected.
>
> This isn't too surprising. Presumably the app caches some duration while it's streaming. Would be interesting to know how long it will play when this happens.
In a recent play, I just left the house and left my wifi, I opened my app in the car and got about 3-5 min away when it stopped and I noticed it wasn't connected to my server. I killed the app and reconnected and it played fine.
I agree that it seems that the app is automatically playing from the cache. I think I'd prefer it if it wouldn't autoplay when I open the app.
@advplyr commented on GitHub (Feb 8, 2024):
Is anyone able to reproduce this consistently yet? I'm trying to reproduce it again but unsuccessful so far.
By reproduce consistently I mean you are able to cause this to happen with a specific set of steps that you can share.
I've taken a guess at what could be happening while reading through the docs but I can't be sure until I can reproduce it. https://developer.apple.com/documentation/avfaudio/avaudiosession/interruptionreason/appwassuspended
I'll test it asap. I made attempts to trigger this intentionally (to try to gauge a cause/effect) for about 20 min yesterday and couldn't get it to happen. Then it happened (seemingly randomly) when I opened the app last night.... and then again just now when I opened up the app to check what version I had installed (0.9.71). I'll update again next week if I do or don't see it again (after updating).
@mdeeter commented on GitHub (Feb 12, 2024):
I'll test it asap. I made attempts to trigger this intentionally (to try to gauge a cause/effect) for about 20 min yesterday and couldn't get it to happen. Then it happened (seemingly randomly) when I opened the app last night.... and then again just now when I opened up the app to check what version I had installed (0.9.71). I'll update again next week if I do or don't see it again (after updating).
So this is continuing to happen to me in the latest version (0.9.72). Idk if this is related, but I also experienced my current book starting to play at 1-2 AM seemingly on it's own.
This is really weird. I wonder if there's some logging that could be enabled (perhaps that I could opt-into) that could cache interactions that I could then send you (or upload here) to help triage this issue.
@mdeeter commented on GitHub (Feb 16, 2024):
So this is continuing to happen to me in the latest version (0.9.72). Idk if this is related, but I also experienced my current book starting to play at 1-2 AM seemingly on it's own.
This is really weird. I wonder if there's some logging that could be enabled (perhaps that I could opt-into) that could cache interactions that I could then send you (or upload here) to help triage this issue.
If we're right that this is a caching issue, the server may not even know. Thus, logs may not be entirely useful.
@dathbe commented on GitHub (Feb 16, 2024):
If we're right that this is a caching issue, the server may not even know. Thus, logs may not be entirely useful.
I experienced an extreme example of this last night where a book started playing randomly at midnight. The phone was otherwise sitting peacefully on my nightstand. When I opened the app to stop it, I was greeted with this:
There was at least one, if not 2 more copies of the error message on the screen when I first opened it, and they were disappearing quickly. I didn't have my full senses about me, but I don't believe I had the option to stop the playback from within the app and had to force quit the app to get playback to stop (i.e., the playback controls were missing).
Steps to repeat:
Open app from force-closed state
Play book for about 2-5 minutes
Pause book (I think i used the in-app controls for this, but it's possible I used the lock screen widget)
Switch to a different app, but leave player open in background
About 8 hours later, playback randomly restarted
I had not touched the app since pausing.
@dathbe commented on GitHub (Feb 16, 2024):
I experienced an extreme example of this last night where a book started playing randomly at midnight. The phone was otherwise sitting peacefully on my nightstand. When I opened the app to stop it, I was greeted with this:

There was at least one, if not 2 more copies of the error message on the screen when I first opened it, and they were disappearing quickly. I didn't have my full senses about me, but I don't believe I had the option to stop the playback from within the app and had to force quit the app to get playback to stop (i.e., the playback controls were missing).
Steps to repeat:
1. Open app from force-closed state
2. Play book for about 2-5 minutes
3. Pause book (I think i used the in-app controls for this, but it's possible I used the lock screen widget)
4. Switch to a different app, but leave player open in background
5. About 8 hours later, playback randomly restarted
I had not touched the app since pausing.
I experienced an extreme example of this last night where a book started playing randomly at midnight. The phone was otherwise sitting peacefully on my nightstand. When I opened the app to stop it, I was greeted with this:
There was at least one, if not 2 more copies of the error message on the screen when I first opened it, and they were disappearing quickly. I didn't have my full senses about me, but I don't believe I had the option to stop the playback from within the app and had to force quit the app to get playback to stop (i.e., the playback controls were missing).
Steps to repeat:
Open app from force-closed state.
Play book for about 2-5 minutes
Pause book (I think i used the in-app controls for this, but it's possible I used the lock screen widget)
About 8 hours later, playback randomly restarted
I had not touched the app since pausing.
It also started playing at night here as well randomly. It had been a few hours since I last used it.
@RealWalts commented on GitHub (Feb 16, 2024):
> I experienced an extreme example of this last night where a book started playing randomly at midnight. The phone was otherwise sitting peacefully on my nightstand. When I opened the app to stop it, I was greeted with this:
>
> There was at least one, if not 2 more copies of the error message on the screen when I first opened it, and they were disappearing quickly. I didn't have my full senses about me, but I don't believe I had the option to stop the playback from within the app and had to force quit the app to get playback to stop (i.e., the playback controls were missing).
>
> Steps to repeat:
>
> 1. Open app from force-closed state.
> 2. Play book for about 2-5 minutes
> 3. Pause book (I think i used the in-app controls for this, but it's possible I used the lock screen widget)
> 4. About 8 hours later, playback randomly restarted
>
> I had not touched the app since pausing.
It also started playing at night here as well randomly. It had been a few hours since I last used it.
I know it was mentioned that this also happens while streaming but the screenshots I've seen so far have all been downloaded. Is it possible the streaming is a slightly different situation happening that is getting conflated with this one? Because that happens often and makes it difficult to narrow down the issue.
@advplyr commented on GitHub (Feb 16, 2024):
I know it was mentioned that this also happens while streaming but the screenshots I've seen so far have all been downloaded. Is it possible the streaming is a slightly different situation happening that is getting conflated with this one? Because that happens often and makes it difficult to narrow down the issue.
I'm currently on book 16 of Dresden Files... I've been streaming this series since book 10 and still seeing this issue... so I don't think it's specific to downloaded vs streaming.
@mdeeter commented on GitHub (Feb 16, 2024):
I'm currently on book 16 of Dresden Files... I've been streaming this series since book 10 and still seeing this issue... so I don't think it's specific to downloaded vs streaming.
I'm surprised you haven't been able to reproduce this. I just tried it again (play, pause, don't force close, wait many hours, open app) and it did it again. I have a habit of force closing apps, so I think I'm 3 for 3 when leaving it in the background and having it play when re-opening.
@dathbe commented on GitHub (Feb 18, 2024):
I'm surprised you haven't been able to reproduce this. I just tried it again (play, pause, don't force close, wait many hours, open app) and it did it again. I have a habit of force closing apps, so I think I'm 3 for 3 when leaving it in the background and having it play when re-opening.
I have this issue too on latest ios 17.3.1 and latest ABS ios app version 0.9.72 beta
It seems like after the ABS app is in the background for a while, it forgets its playback state even though it's for sure paused. When opening the app it resumes to become playing BUT WITHOUT the miniplayer coming up
@nigiriemoji commented on GitHub (Feb 23, 2024):
I have this issue too on latest ios 17.3.1 and latest ABS ios app version 0.9.72 beta
It seems like after the ABS app is in the background for a while, it forgets its playback state even though it's for sure paused. When opening the app it resumes to become playing BUT WITHOUT the miniplayer coming up
I have this issue too on latest ios and latest ABS ios app version
Would you mind adding the version numbers instead of just latest, since that can help with future debugging when reviewing old issues? Assuming that's 0.9.72
@nichwall commented on GitHub (Feb 23, 2024):
> I have this issue too on latest ios and latest ABS ios app version
Would you mind adding the version numbers instead of just `latest`, since that can help with future debugging when reviewing old issues? Assuming that's 0.9.72
I have this issue too on latest ios and latest ABS ios app version
Would you mind adding the version numbers instead of just latest, since that can help with future debugging when reviewing old issues? Assuming that's 0.9.72
done, thank you. any logs i can provide to help?
@nigiriemoji commented on GitHub (Feb 23, 2024):
> > I have this issue too on latest ios and latest ABS ios app version
>
> Would you mind adding the version numbers instead of just `latest`, since that can help with future debugging when reviewing old issues? Assuming that's 0.9.72
done, thank you. any logs i can provide to help?
Here is a video of the exact bug that I’m experiencing.
I was playing an audiobook a few hours ago. The ABS app v0.9.72 stays in background apps for iOS 17.3.1, then when I open up the app the play continues to resume. Note that the mini player at the bottom does NOT show up at the bottom. It does if I manually hit play, but not when encountering this bug
Server Log Level
2024-02-27 03:45:29.246
INFO
[SocketAuthority] Socket Connected N9VHAZFqL21fdDG4AABb
2024-02-27 03:45:29.716
INFO
[PlaybackSessionManager] Syncing local session "Real Tigers" (1e47c6cb-8558-46e4-a72e-d37947abc8f0)
2024-02-27 03:45:35.872
INFO
[PlaybackSessionManager] startSession: Closing open session "Real Tigers" for user "adminABS" (Device: iPhone16,2 / v0.9.72)
2024-02-27 03:46:10.010
INFO
[SocketAuthority] Socket N9VHAZFqL21fdDG4AABb disconnected from client "adminABS" after 40764ms (Reason: transport close)
@nigiriemoji commented on GitHub (Feb 27, 2024):
Here is a video of the exact bug that I’m experiencing.
I was playing an audiobook a few hours ago. The ABS app v0.9.72 stays in background apps for iOS 17.3.1, then when I open up the app the play continues to resume. Note that the mini player at the bottom does NOT show up at the bottom. It does if I manually hit play, but not when encountering this bug
https://github.com/advplyr/audiobookshelf-app/assets/53108354/d158c905-84df-4775-9860-82a7f8c83927
These are my logs:
```
Server Log Level
2024-02-27 03:45:29.246
INFO
[SocketAuthority] Socket Connected N9VHAZFqL21fdDG4AABb
2024-02-27 03:45:29.716
INFO
[PlaybackSessionManager] Syncing local session "Real Tigers" (1e47c6cb-8558-46e4-a72e-d37947abc8f0)
2024-02-27 03:45:35.872
INFO
[PlaybackSessionManager] startSession: Closing open session "Real Tigers" for user "adminABS" (Device: iPhone16,2 / v0.9.72)
2024-02-27 03:46:10.010
INFO
[SocketAuthority] Socket N9VHAZFqL21fdDG4AABb disconnected from client "adminABS" after 40764ms (Reason: transport close)
```
That’s effectively identical to what I experience. I’m using an iPhone 13 mini in case that’s making a difference.
@dathbe commented on GitHub (Feb 27, 2024):
That’s effectively identical to what I experience. I’m using an iPhone 13 mini in case that’s making a difference.
@nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
@advplyr commented on GitHub (Feb 27, 2024):
@nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
@nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
@advplyr
I can sort of consistently reproduce it with many minutes/hours between each playback session. I just don’t know how many minutes to wait, but taking a night’s sleep usually is long enough. Just happened to me right now this morning.
Open ABS app on iOS
Play any audiobook
Eventually manually pause it or set a sleep timer (I experienced bug both ways)
Leave ABS app by swiping up to Home Screen, browse other apps, whatever. But ensure that the ABS app remains in the background but not fully closed (as in DO NOT swipe the app away to kill/terminate it in the app switcher screen)
Don’t use ABS app for an hour or more (overnight sleep is long enough)
Open up ABS app
Experience automatic playback bug
@nigiriemoji commented on GitHub (Feb 27, 2024):
> @nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
@advplyr
I can sort of consistently reproduce it with many minutes/hours between each playback session. I just don’t know how many minutes to wait, but taking a night’s sleep usually is long enough. Just happened to me right now this morning.
1. Open ABS app on iOS
2. Play any audiobook
3. Eventually manually pause it or set a sleep timer (I experienced bug both ways)
4. Leave ABS app by swiping up to Home Screen, browse other apps, whatever. But ensure that the ABS app remains in the background but not fully closed (as in DO NOT swipe the app away to kill/terminate it in the app switcher screen)
5. Don’t use ABS app for an hour or more (overnight sleep is long enough)
6. Open up ABS app
7. Experience automatic playback bug
Adding another recording of the bug. Haven’t used ABS app in several hours, feels like something to do with it being in the background for so long that it forgets its playback state?
@nigiriemoji commented on GitHub (Feb 28, 2024):
Adding another recording of the bug. Haven’t used ABS app in several hours, feels like something to do with it being in the background for so long that it forgets its playback state?
https://github.com/advplyr/audiobookshelf-app/assets/53108354/8b44bc1c-1b10-43d2-a51c-67ba8a3ab275
I think the timing thing is important. I tried after about an hour and the app opened fine. But after 12 the bug occurred. Also, I left the app on the book screen (did not back out to the bookshelf) when I switched apps. That may or may not matter. So just pause and swipe up to switch apps, don’t press back to leave the book page.
@dathbe commented on GitHub (Feb 28, 2024):
I think the timing thing is important. I tried after about an hour and the app opened fine. But after 12 the bug occurred. Also, I left the app on the book screen (did not back out to the bookshelf) when I switched apps. That may or may not matter. So just pause and swipe up to switch apps, don’t press back to leave the book page.
@nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
@advplyr
I can sort of consistently reproduce it with many minutes/hours between each playback session. I just don’t know how many minutes to wait, but taking a night’s sleep usually is long enough. Just happened to me right now this morning.
Open ABS app on iOS
Play any audiobook
Eventually manually pause it or set a sleep timer (I experienced bug both ways)
Leave ABS app by swiping up to Home Screen, browse other apps, whatever. But ensure that the ABS app remains in the background but not fully closed (as in DO NOT swipe the app away to kill/terminate it in the app switcher screen)
Don’t use ABS app for an hour or more (overnight sleep is long enough)
Open up ABS app
Experience automatic playback bug
I tested this with a book streaming and let it play for about 10 minutes in the background with the screen off. I paused from the lock screen and just left the device for a little over 12 hours. I just unlocked the device and opened the app (that was still open in the background) and the bug did not occur.
I'm still on iOS 16.x, haven't updated to 17 yet. It seems everyone here is on 17 so maybe this bug started on newer iOS versions. Is anyone still on iOS 16 that is having this issue?
@advplyr commented on GitHub (Feb 28, 2024):
> > @nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
>
> @advplyr
>
> I can sort of consistently reproduce it with many minutes/hours between each playback session. I just don’t know how many minutes to wait, but taking a night’s sleep usually is long enough. Just happened to me right now this morning.
>
> 1. Open ABS app on iOS
> 2. Play any audiobook
> 3. Eventually manually pause it or set a sleep timer (I experienced bug both ways)
> 4. Leave ABS app by swiping up to Home Screen, browse other apps, whatever. But ensure that the ABS app remains in the background but not fully closed (as in DO NOT swipe the app away to kill/terminate it in the app switcher screen)
> 5. Don’t use ABS app for an hour or more (overnight sleep is long enough)
> 6. Open up ABS app
> 7. Experience automatic playback bug
I tested this with a book streaming and let it play for about 10 minutes in the background with the screen off. I paused from the lock screen and just left the device for a little over 12 hours. I just unlocked the device and opened the app (that was still open in the background) and the bug did not occur.
I'm still on iOS 16.x, haven't updated to 17 yet. It seems everyone here is on 17 so maybe this bug started on newer iOS versions. Is anyone still on iOS 16 that is having this issue?
@nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
I tested this with a book streaming and let it play for about 10 minutes in the background with the screen off. I paused from the lock screen and just left the device for a little over 12 hours. I just unlocked the device and opened the app (that was still open in the background) and the bug did not occur.
I'm still on iOS 16.x, haven't updated to 17 yet. It seems everyone here is on 17 so maybe this bug started on newer iOS versions. Is anyone still on iOS 16 that is having this issue?
Also on iOS 17 sorry. I typically pause directly within the app, though unsure what is the last screen/menu of the app that causes the bug
Any logs that I could provide to you the next time I encounter this bug?
@nigiriemoji commented on GitHub (Feb 28, 2024):
> > > @nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
> >
> >
>
> I tested this with a book streaming and let it play for about 10 minutes in the background with the screen off. I paused from the lock screen and just left the device for a little over 12 hours. I just unlocked the device and opened the app (that was still open in the background) and the bug did not occur.
>
> I'm still on iOS 16.x, haven't updated to 17 yet. It seems everyone here is on 17 so maybe this bug started on newer iOS versions. Is anyone still on iOS 16 that is having this issue?
Also on iOS 17 sorry. I typically pause directly within the app, though unsure what is the last screen/menu of the app that causes the bug
Any logs that I could provide to you the next time I encounter this bug?
I tested pausing within the app and left it in the bg asleep for a day. Still not able to reproduce that on iOS 16.
I don't know about any logs that can provided
@advplyr commented on GitHub (Feb 29, 2024):
I tested pausing within the app and left it in the bg asleep for a day. Still not able to reproduce that on iOS 16.
I don't know about any logs that can provided
I have an iPhone 10 that is only used for testing and iOS 17 isn't supported for it. I will probably get a new one since these types of things are why I opened up donations.
@advplyr commented on GitHub (Feb 29, 2024):
I have an iPhone 10 that is only used for testing and iOS 17 isn't supported for it. I will probably get a new one since these types of things are why I opened up donations.
I had a weird situation this weekend where this bug popped up while I was in the middle of listening. I was running around, so I don't have the exact steps to reproduce, but generally I was listening, and then at some point while the audio was playing I opened the app to find that the controls had disappeared. When I clicked "stream" like I normally do when this bug pops up, the playback went back a couple minutes and started playing again with the control. Very odd.
@dathbe commented on GitHub (Mar 19, 2024):
I had a weird situation this weekend where this bug popped up while I was in the middle of listening. I was running around, so I don't have the exact steps to reproduce, but generally I was listening, and then at some point while the audio was playing I opened the app to find that the controls had disappeared. When I clicked "stream" like I normally do when this bug pops up, the playback went back a couple minutes and started playing again with the control. Very odd.
I continue to have this bug on a daily basis. I'm assuming it won't get resolved until the devs have time/chance to test against iOS 17.
@mdeeter commented on GitHub (Mar 19, 2024):
I continue to have this bug on a daily basis. I'm assuming it won't get resolved until the devs have time/chance to test against iOS 17.
Completely understand. I just wanted to add a new data point in case it's helpful in finding the issue.
I've only encountered the while-listening issue once, and I've just taken to force-closing the app when I'm done listening, so this bug doesn't really bother me. But it will be good to squash it.
@dathbe commented on GitHub (Mar 19, 2024):
Completely understand. I just wanted to add a new data point in case it's helpful in finding the issue.
I've only encountered the while-listening issue once, and I've just taken to force-closing the app when I'm done listening, so this bug doesn't _really_ bother me. But it will be good to squash it.
...More random playing in the middle of the night.
Same as mentioned above... Except that I didn't have to force-cc lose the app. I've been steaming this book... And paused the book around 830pm by removing my airpods. Was awoken to the app playing on its own at 230am.
@mdeeter commented on GitHub (Apr 10, 2024):

...More random playing in the middle of the night.
Same as mentioned above... Except that I didn't have to force-cc lose the app. I've been steaming this book... And paused the book around 830pm by removing my airpods. Was awoken to the app playing on its own at 230am.
I haven't had it happen on the latest update, but I also have gotten into the habit of force-closing the app when I'm done. Let me see if I can get it to happen again.
@dathbe commented on GitHub (May 22, 2024):
I haven't had it happen on the latest update, but I also have gotten into the habit of force-closing the app when I'm done. Let me see if I can get it to happen again.
I'm going off a small sample size (1), but I did not get this error with the latest version after trying what had caused it before. So it's entirely possible 0.9.74 has a fix. Anyone else?
@dathbe commented on GitHub (May 23, 2024):
I'm going off a small sample size (1), but I did not get this error with the latest version after trying what had caused it before. So it's entirely possible 0.9.74 has a fix. Anyone else?
usually the bug was play book, sleep timer activates, come back to app ~1 hour later and auto play without input being the bug
no longer occurs
@nigiriemoji commented on GitHub (May 23, 2024):
+1 seems to be fixed after three sessions
usually the bug was play book, sleep timer activates, come back to app ~1 hour later and auto play without input being the bug
no longer occurs
I managed to get the playback error once yesterday in a whole day of listening, but far more rarely than before. Perhaps an unrelated issue, since I didn't have any unexpected resumes
@benonymity commented on GitHub (May 25, 2024):
I managed to get the playback error once yesterday in a whole day of listening, but far more rarely than before. Perhaps an unrelated issue, since I didn't have any unexpected resumes
Can anyone still reproduce this issue with latest 2.18.1 server and 0.9.78 client? @benonymity @mdeeter?
@bloodscript commented on GitHub (Jan 22, 2025):
Can anyone still reproduce this issue with latest 2.18.1 server and 0.9.78 client? @benonymity @mdeeter?
I haven't seen this occur in quite a long time... unsure if it's from an iOS update (I'm on 18.2.1) or ABS update (I'm on 0.9.78).
@mdeeter commented on GitHub (Jan 22, 2025):
I haven't seen this occur in quite a long time... unsure if it's from an iOS update (I'm on 18.2.1) or ABS update (I'm on 0.9.78).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @mdeeter on GitHub (Dec 7, 2023).
Steps to reproduce
Expected behaviour
Actual behaviour
Environment data
Audiobookshelf Version: 2.5.0
iOS Issue
iOS Version: 17.1.2
iPhone model: iPhone 12 Pro
@advplyr commented on GitHub (Dec 8, 2023):
I'm not able to reproduce this. What version of the iOS app are you using?
Is this happening every time for you? Are you leaving the app open in the background or closing it?
@mdeeter commented on GitHub (Dec 9, 2023):
app version
0.9.68-beta(updated in og description)I typically always switch apps (leaving apps in the bg)... until something doesn't seem to be working, then I'll hard-close the app and re-open it.
It's happened several times in the past week, but it doesn't seem to happen all of the time... often enough to be a little annoying :)
@mdeeter commented on GitHub (Dec 9, 2023):
Just happened again...
I put in my airpods... Unlocked my phone... Opened the app...
The book started playing immediately... Here's the ui
Then I try tapping on the book... But it won't open until the ui finishes loading...

Then the book opens (it's still playing) and there's no player UI showing...

I click play button and it pauses the book and it shows the player UI at the bottom...

@KaiStarkk commented on GitHub (Dec 18, 2023):
It’s a weird one. I get the same issue. Doesn’t really bother me but still, curious.
@dathbe commented on GitHub (Dec 20, 2023):
I experienced this same issue. Here are some additional details in case it is helpful in recreating:
I was listening to a book on my iPhone in the car via Bluetooth.
I then switched the car to play a different audio source (though I don't think I explicitly paused Audiobookshelf)
I then was listening on my phone to the same book via headphones.
I then paused the book in my phone.
I then listened to the book on my iPad via headphones.
I paused the iPad.
Both devices were put down for several hours, but the app was not killed on either device.
When I picked up the phone several hours later, this issue popped up.
The immediately-start-playing issue doesn't bother me too much (I would hate to have a fix for this prevent being able to get in and out of a car and continue listening without a bunch of button presses), but I experienced a secondary issue where the controls were not visible while the book was playing. Possibly the same as OP's "before the UI is finished loading."
P.S. I meant to mention that major kudos are deserved fro the developers of this app. This is one of the best if not the best open source iOS apps I've experienced. It looks beautiful, runs smoothly, and does what it's supposed to. This is the one bug that I've found so far.
@RealWalts commented on GitHub (Dec 22, 2023):
I also have the same issue, it used to happen before but seems to got fixed. But now it's back.
Also not a big issue, i usually just press play again and it continues with the controls.
@livineasy629 commented on GitHub (Dec 27, 2023):
This happens whether the book is downloaded or streaming. The streaming one is way more confusing because it starts playing the audio even before the server connects.
When I go to the book that's playing it shows as if it isn't playing.
This is also happening on the macOS client which seems to be the iOS app running on Mac. It randomly starts playing there and I can't get the play controls to come up so I have to quit the app.
I just updated the server app so I'll test it this week and report back.
@livineasy629 commented on GitHub (Jan 3, 2024):
Still present on the latest server version and updated iOS app. It will even continue playing a file that isn't downloaded while the server is disconnected.
@dathbe commented on GitHub (Jan 4, 2024):
This isn't too surprising. Presumably the app caches some duration while it's streaming. Would be interesting to know how long it will play when this happens.
@GiladHi commented on GitHub (Feb 5, 2024):
I also have the same issue with the latest version...
@mdeeter commented on GitHub (Feb 6, 2024):
In a recent play, I just left the house and left my wifi, I opened my app in the car and got about 3-5 min away when it stopped and I noticed it wasn't connected to my server. I killed the app and reconnected and it played fine.
I agree that it seems that the app is automatically playing from the cache. I think I'd prefer it if it wouldn't autoplay when I open the app.
@advplyr commented on GitHub (Feb 8, 2024):
Is anyone able to reproduce this consistently yet? I'm trying to reproduce it again but unsuccessful so far.
By reproduce consistently I mean you are able to cause this to happen with a specific set of steps that you can share.
I've taken a guess at what could be happening while reading through the docs but I can't be sure until I can reproduce it. https://developer.apple.com/documentation/avfaudio/avaudiosession/interruptionreason/appwassuspended
@advplyr commented on GitHub (Feb 12, 2024):
Let me know if this issue persists in 0.9.72-beta
@mdeeter commented on GitHub (Feb 12, 2024):
I'll test it asap. I made attempts to trigger this intentionally (to try to gauge a cause/effect) for about 20 min yesterday and couldn't get it to happen. Then it happened (seemingly randomly) when I opened the app last night.... and then again just now when I opened up the app to check what version I had installed (0.9.71). I'll update again next week if I do or don't see it again (after updating).
@mdeeter commented on GitHub (Feb 16, 2024):
So this is continuing to happen to me in the latest version (0.9.72). Idk if this is related, but I also experienced my current book starting to play at 1-2 AM seemingly on it's own.
This is really weird. I wonder if there's some logging that could be enabled (perhaps that I could opt-into) that could cache interactions that I could then send you (or upload here) to help triage this issue.
@dathbe commented on GitHub (Feb 16, 2024):
If we're right that this is a caching issue, the server may not even know. Thus, logs may not be entirely useful.
@GiladHi commented on GitHub (Feb 16, 2024):
Still happened with the latest build, even with downloaded local files.
@advplyr commented on GitHub (Feb 16, 2024):
The best way to figure this out is to find out how to reproduce it
@dathbe commented on GitHub (Feb 16, 2024):
I experienced an extreme example of this last night where a book started playing randomly at midnight. The phone was otherwise sitting peacefully on my nightstand. When I opened the app to stop it, I was greeted with this:
There was at least one, if not 2 more copies of the error message on the screen when I first opened it, and they were disappearing quickly. I didn't have my full senses about me, but I don't believe I had the option to stop the playback from within the app and had to force quit the app to get playback to stop (i.e., the playback controls were missing).
Steps to repeat:
I had not touched the app since pausing.
@RealWalts commented on GitHub (Feb 16, 2024):
It also started playing at night here as well randomly. It had been a few hours since I last used it.
@advplyr commented on GitHub (Feb 16, 2024):
I know it was mentioned that this also happens while streaming but the screenshots I've seen so far have all been downloaded. Is it possible the streaming is a slightly different situation happening that is getting conflated with this one? Because that happens often and makes it difficult to narrow down the issue.
@dathbe commented on GitHub (Feb 16, 2024):
This book was not downloaded -- at least not manually.
@mdeeter commented on GitHub (Feb 16, 2024):
I'm currently on book 16 of Dresden Files... I've been streaming this series since book 10 and still seeing this issue... so I don't think it's specific to downloaded vs streaming.
@dathbe commented on GitHub (Feb 18, 2024):
I'm surprised you haven't been able to reproduce this. I just tried it again (play, pause, don't force close, wait many hours, open app) and it did it again. I have a habit of force closing apps, so I think I'm 3 for 3 when leaving it in the background and having it play when re-opening.
@nigiriemoji commented on GitHub (Feb 23, 2024):
I have this issue too on latest ios 17.3.1 and latest ABS ios app version 0.9.72 beta
It seems like after the ABS app is in the background for a while, it forgets its playback state even though it's for sure paused. When opening the app it resumes to become playing BUT WITHOUT the miniplayer coming up
@nichwall commented on GitHub (Feb 23, 2024):
Would you mind adding the version numbers instead of just
latest, since that can help with future debugging when reviewing old issues? Assuming that's 0.9.72@nigiriemoji commented on GitHub (Feb 23, 2024):
done, thank you. any logs i can provide to help?
@nigiriemoji commented on GitHub (Feb 27, 2024):
Here is a video of the exact bug that I’m experiencing.
I was playing an audiobook a few hours ago. The ABS app v0.9.72 stays in background apps for iOS 17.3.1, then when I open up the app the play continues to resume. Note that the mini player at the bottom does NOT show up at the bottom. It does if I manually hit play, but not when encountering this bug
https://github.com/advplyr/audiobookshelf-app/assets/53108354/d158c905-84df-4775-9860-82a7f8c83927
These are my logs:
@dathbe commented on GitHub (Feb 27, 2024):
That’s effectively identical to what I experience. I’m using an iPhone 13 mini in case that’s making a difference.
@mdeeter commented on GitHub (Feb 27, 2024):
yes, that's the exact same UX I have as well
@advplyr commented on GitHub (Feb 27, 2024):
@nigiriemoji Are you able to reproduce this consistently? To where you can give me an exact set of steps to reproduce it on my end?
@nigiriemoji commented on GitHub (Feb 27, 2024):
@advplyr
I can sort of consistently reproduce it with many minutes/hours between each playback session. I just don’t know how many minutes to wait, but taking a night’s sleep usually is long enough. Just happened to me right now this morning.
@nigiriemoji commented on GitHub (Feb 28, 2024):
Adding another recording of the bug. Haven’t used ABS app in several hours, feels like something to do with it being in the background for so long that it forgets its playback state?
https://github.com/advplyr/audiobookshelf-app/assets/53108354/8b44bc1c-1b10-43d2-a51c-67ba8a3ab275
@dathbe commented on GitHub (Feb 28, 2024):
I think the timing thing is important. I tried after about an hour and the app opened fine. But after 12 the bug occurred. Also, I left the app on the book screen (did not back out to the bookshelf) when I switched apps. That may or may not matter. So just pause and swipe up to switch apps, don’t press back to leave the book page.
@advplyr commented on GitHub (Feb 28, 2024):
I tested this with a book streaming and let it play for about 10 minutes in the background with the screen off. I paused from the lock screen and just left the device for a little over 12 hours. I just unlocked the device and opened the app (that was still open in the background) and the bug did not occur.
I'm still on iOS 16.x, haven't updated to 17 yet. It seems everyone here is on 17 so maybe this bug started on newer iOS versions. Is anyone still on iOS 16 that is having this issue?
@dathbe commented on GitHub (Feb 28, 2024):
I don't have any devices on ios 16 anymore. But try pausing from within the app and then switching apps.
@nigiriemoji commented on GitHub (Feb 28, 2024):
Also on iOS 17 sorry. I typically pause directly within the app, though unsure what is the last screen/menu of the app that causes the bug
Any logs that I could provide to you the next time I encounter this bug?
@advplyr commented on GitHub (Feb 29, 2024):
I tested pausing within the app and left it in the bg asleep for a day. Still not able to reproduce that on iOS 16.
I don't know about any logs that can provided
@mdeeter commented on GitHub (Feb 29, 2024):
this still happens to me daily... any idea when you might be able to test on iOS 17?
@advplyr commented on GitHub (Feb 29, 2024):
I have an iPhone 10 that is only used for testing and iOS 17 isn't supported for it. I will probably get a new one since these types of things are why I opened up donations.
@nigiriemoji commented on GitHub (Mar 6, 2024):
This issue is still occurring for v0.9.73-beta iOS that came out in the last 48 hours.
@dathbe commented on GitHub (Mar 19, 2024):
I had a weird situation this weekend where this bug popped up while I was in the middle of listening. I was running around, so I don't have the exact steps to reproduce, but generally I was listening, and then at some point while the audio was playing I opened the app to find that the controls had disappeared. When I clicked "stream" like I normally do when this bug pops up, the playback went back a couple minutes and started playing again with the control. Very odd.
@mdeeter commented on GitHub (Mar 19, 2024):
I continue to have this bug on a daily basis. I'm assuming it won't get resolved until the devs have time/chance to test against iOS 17.
@advplyr commented on GitHub (Mar 19, 2024):
Yeah I still have to buy a newer iphone
@dathbe commented on GitHub (Mar 19, 2024):
Completely understand. I just wanted to add a new data point in case it's helpful in finding the issue.
I've only encountered the while-listening issue once, and I've just taken to force-closing the app when I'm done listening, so this bug doesn't really bother me. But it will be good to squash it.
@advplyr commented on GitHub (Mar 19, 2024):
For sure, I appreciate the reports since we haven't narrowed down how exactly to reproduce this.
@mdeeter commented on GitHub (Apr 10, 2024):
...More random playing in the middle of the night.
Same as mentioned above... Except that I didn't have to force-cc lose the app. I've been steaming this book... And paused the book around 830pm by removing my airpods. Was awoken to the app playing on its own at 230am.
@advplyr commented on GitHub (May 22, 2024):
Can anyone confirm if this issue still exists in v0.9.74-beta?
@advplyr commented on GitHub (May 22, 2024):
I bought a new iphone that is running ios17 and I haven't come across this yet
@dathbe commented on GitHub (May 22, 2024):
I haven't had it happen on the latest update, but I also have gotten into the habit of force-closing the app when I'm done. Let me see if I can get it to happen again.
@nichwall commented on GitHub (May 22, 2024):
May have been inadvertently fixed by https://github.com/advplyr/audiobookshelf-app/pull/1179?
@dathbe commented on GitHub (May 23, 2024):
I'm going off a small sample size (1), but I did not get this error with the latest version after trying what had caused it before. So it's entirely possible 0.9.74 has a fix. Anyone else?
@nigiriemoji commented on GitHub (May 23, 2024):
+1 seems to be fixed after three sessions
usually the bug was play book, sleep timer activates, come back to app ~1 hour later and auto play without input being the bug
no longer occurs
@advplyr commented on GitHub (May 23, 2024):
Awesome thanks for testing and thanks to @indiefan for tracking that one down
@benonymity commented on GitHub (May 25, 2024):
I managed to get the playback error once yesterday in a whole day of listening, but far more rarely than before. Perhaps an unrelated issue, since I didn't have any unexpected resumes
@bloodscript commented on GitHub (Jan 22, 2025):
Can anyone still reproduce this issue with latest 2.18.1 server and 0.9.78 client? @benonymity @mdeeter?
@mdeeter commented on GitHub (Jan 22, 2025):
I haven't seen this occur in quite a long time... unsure if it's from an iOS update (I'm on 18.2.1) or ABS update (I'm on 0.9.78).