Originally created by @dathbe on GitHub (Dec 20, 2023).
Steps to reproduce
I have not tried to recreate the issue yet, but it happened this morning when:
Was listening to App
Exited (did not completely close) App
Let it sit for a while
Open app again
Last listened to book started playing automatically, but there were no controls at the bottom of the screen to pause it. The only way I could pause was to slide down from the top to get the controls on the widgets screen. Or, I suppose I could have killed the app.
Expected behaviour
I can't say whether the book is supposed to immediately pick up and start playing (that might be useful in the car or in other situations where hands and eye contact are at a premium). But the controls should be visible any time a book is playing.
Actual behaviour
As I said above, the controls were not visible anywhere. Maybe this is user error (I was just able to get into the Beta yesterday), but I would expect the controls to be available at the bottom of the window.
It's not exactly visible in this photo, but the book is playing at the time I took this screenshot. Am I missing something, or should there be some controls at the bottom of the screen (that when clicked pull up the full-screen controls).
Some notes on possibly recreating this to help recreating the issue:
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.
Environment data
Audiobookshelf Version: 2.6.0
Android App?
iOS App?
iOS Issue
iOS Version: 17.1.2
iPhone model: 13 mini
Originally created by @dathbe on GitHub (Dec 20, 2023).
### Steps to reproduce
I have not tried to recreate the issue yet, but it happened this morning when:
1. Was listening to App
2. Exited (did not completely close) App
3. Let it sit for a while
4. Open app again
5. Last listened to book started playing automatically, but there were no controls at the bottom of the screen to pause it. The only way I could pause was to slide down from the top to get the controls on the widgets screen. Or, I suppose I could have killed the app.
### Expected behaviour
I can't say whether the book is supposed to immediately pick up and start playing (that might be useful in the car or in other situations where hands and eye contact are at a premium). But the controls should be visible any time a book is playing.
### Actual behaviour
As I said above, the controls were not visible anywhere. Maybe this is user error (I was just able to get into the Beta yesterday), but I would expect the controls to be available at the bottom of the window.

It's not exactly visible in this photo, but the book is playing at the time I took this screenshot. Am I missing something, or should there be some controls at the bottom of the screen (that when clicked pull up the full-screen controls).
Some notes on possibly recreating this to help recreating the issue:
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.
### Environment data
Audiobookshelf Version: 2.6.0
- [ ] Android App?
- [x] iOS App?
#### iOS Issue
iOS Version: 17.1.2
iPhone model: 13 mini
adam
added the bug label 2026-04-24 23:38:49 +02:00
The book is not supposed to start playing automatically. I haven't been able to reproduce it yet but it was brought up already here #973
@advplyr commented on GitHub (Dec 20, 2023):
The book is not supposed to start playing automatically. I haven't been able to reproduce it yet but it was brought up already here #973
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 @dathbe on GitHub (Dec 20, 2023).
Steps to reproduce
I have not tried to recreate the issue yet, but it happened this morning when:
Expected behaviour
I can't say whether the book is supposed to immediately pick up and start playing (that might be useful in the car or in other situations where hands and eye contact are at a premium). But the controls should be visible any time a book is playing.
Actual behaviour
As I said above, the controls were not visible anywhere. Maybe this is user error (I was just able to get into the Beta yesterday), but I would expect the controls to be available at the bottom of the window.

It's not exactly visible in this photo, but the book is playing at the time I took this screenshot. Am I missing something, or should there be some controls at the bottom of the screen (that when clicked pull up the full-screen controls).
Some notes on possibly recreating this to help recreating the issue:
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.
Environment data
Audiobookshelf Version: 2.6.0
iOS Issue
iOS Version: 17.1.2
iPhone model: 13 mini
@advplyr commented on GitHub (Dec 20, 2023):
The book is not supposed to start playing automatically. I haven't been able to reproduce it yet but it was brought up already here #973
@advplyr commented on GitHub (Dec 20, 2023):
Duplicate of #973