Originally created by @tali055 on GitHub (Feb 26, 2025).
What was the Problem?
This started with a recent app update, the tabs for continueing and currently listening in the Android Auto app are suddenly not showing up anymore, only the browse and downloads tabs are there.
Steps to Reproduce the Issue
Open Android Auto app in the car
Continue and Currently Listening tabs are gone
What was Expected?
There used to be two tabs to the left of browse and downloads for the currently listening books where you could easily continue.
Phone Model
Samsung Galaxy A54
Phone OS
Android 14
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
Additional Notes
No response
Originally created by @tali055 on GitHub (Feb 26, 2025).
### What was the Problem?
This started with a recent app update, the tabs for continueing and currently listening in the Android Auto app are suddenly not showing up anymore, only the browse and downloads tabs are there.
### Steps to Reproduce the Issue
1. Open Android Auto app in the car
2. Continue and Currently Listening tabs are gone
### What was Expected?
There used to be two tabs to the left of browse and downloads for the currently listening books where you could easily continue.
### Phone Model
Samsung Galaxy A54
### Phone OS
Android 14
### Audiobookshelf App Version
Android App - 0.9.79
### Installation Source
Google Play Store
### Additional Notes
_No response_
adam
added the bug label 2026-04-24 23:51:32 +02:00
for me this has been happening randomly for a long time. Sometimes it automatically continues las playing book, sometimes it shows continue listening and sometimes only browse and download appears. I have been trying to reproduce it consistendly but wasn't able. My first tought it was related to bad connection(since it normally hapens on the garage were the connection is usually poor) but i seem it happen also on cases with good connection so no idea why.
Phone Model
Pixel 8
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
@ttvAmavisca commented on GitHub (Mar 3, 2025):
for me this has been happening randomly for a long time. Sometimes it automatically continues las playing book, sometimes it shows continue listening and sometimes only browse and download appears. I have been trying to reproduce it consistendly but wasn't able. My first tought it was related to bad connection(since it normally hapens on the garage were the connection is usually poor) but i seem it happen also on cases with good connection so no idea why.
Phone Model
Pixel 8
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
for me this has been happening randomly for a long time. Sometimes it automatically continues las playing book, sometimes it shows continue listening and sometimes only browse and download appears. I have been trying to reproduce it consistendly but wasn't able. My first tought it was related to bad connection(since it normally hapens on the garage were the connection is usually poor) but i seem it happen also on cases with good connection so no idea why.
Phone Model Pixel 8
Phone OS Android 15
Audiobookshelf App Version Android App - 0.9.79
Installation Source Google Play Store
Interesting that it happens on- and off for you, it's constent for me since it started happening about a month ago, seems to not be (only) connection dependent then
@tali055 commented on GitHub (Mar 3, 2025):
> for me this has been happening randomly for a long time. Sometimes it automatically continues las playing book, sometimes it shows continue listening and sometimes only browse and download appears. I have been trying to reproduce it consistendly but wasn't able. My first tought it was related to bad connection(since it normally hapens on the garage were the connection is usually poor) but i seem it happen also on cases with good connection so no idea why.
>
> Phone Model Pixel 8
>
> Phone OS Android 15
>
> Audiobookshelf App Version Android App - 0.9.79
>
> Installation Source Google Play Store
Interesting that it happens on- and off for you, it's constent for me since it started happening about a month ago, seems to not be (only) connection dependent then
Update:
You are right, it happens 100% of the time now.
In multy app(when you have for example google maps + audiobookshelf on the screen) you can only see the recomended on the audiobookshelft part. And if you open it in exclusive, only the library list and downloads shows up
Is there any guide on where to search for the part of the code that handles the android auto app? i may be able to help a bit(i am more of a low level programer but may surpass my hate to java/javascript to help with this XDD)
a quick search only finds ./android/app/src/main/res/xml/automotive_app_desc.xml that is obviusly not it
edit: nevermind, i am already into the vue hell :D
@ttvAmavisca commented on GitHub (Mar 10, 2025):
Update:
You are right, it happens 100% of the time now.
In multy app(when you have for example google maps + audiobookshelf on the screen) you can only see the recomended on the audiobookshelft part. And if you open it in exclusive, only the library list and downloads shows up
Is there any guide on where to search for the part of the code that handles the android auto app? i may be able to help a bit(i am more of a low level programer but may surpass my hate to java/javascript to help with this XDD)
a quick search only finds ./android/app/src/main/res/xml/automotive_app_desc.xml that is obviusly not it
edit: nevermind, i am already into the vue hell :D
I am also having this issue, I decided to take a look to see if I could fix it... I downloaded the latest release (v0.9.81-beta) a few weeks ago, and the problem continued.... So yesterday I cloned the repository, got myself ready to troubleshoot and found that I could not reproduce the issue.... (In fact this morning when I got in the car, I was pleasantly startled when my book resumed without any interaction from me!)
Either this issue has been fixed as of commit cf2f684e80, or there is something about the development build that resolves the error... I'll wait until the next release build and test again.
@lucbelliveau commented on GitHub (May 15, 2025):
I am also having this issue, I decided to take a look to see if I could fix it... I downloaded the latest release (v0.9.81-beta) a few weeks ago, and the problem continued.... So yesterday I cloned the repository, got myself ready to troubleshoot and found that I could not reproduce the issue.... (In fact this morning when I got in the car, I was pleasantly startled when my book resumed without any interaction from me!)
Either this issue has been fixed as of commit cf2f684e80545039d3dc9adaab8f3ecb5c63c6cd, or there is something about the development build that resolves the error... I'll wait until the next release build and test again.
I am also having this issue, I decided to take a look to see if I could fix it... I downloaded the latest release (v0.9.81-beta) a few weeks ago, and the problem continued.... So yesterday I cloned the repository, got myself ready to troubleshoot and found that I could not reproduce the issue.... (In fact this morning when I got in the car, I was pleasantly startled when my book resumed without any interaction from me!)
Either this issue has been fixed as of commit cf2f684, or there is something about the development build that resolves the error... I'll wait until the next release build and test again.
Interesting! I found this issue difficult to reproduce in general, it seems to be erratic whether it happens or not.
@tali055 commented on GitHub (May 15, 2025):
> I am also having this issue, I decided to take a look to see if I could fix it... I downloaded the latest release (v0.9.81-beta) a few weeks ago, and the problem continued.... So yesterday I cloned the repository, got myself ready to troubleshoot and found that I could not reproduce the issue.... (In fact this morning when I got in the car, I was pleasantly startled when my book resumed without any interaction from me!)
>
> Either this issue has been fixed as of commit [cf2f684](https://github.com/advplyr/audiobookshelf-app/commit/cf2f684e80545039d3dc9adaab8f3ecb5c63c6cd), or there is something about the development build that resolves the error... I'll wait until the next release build and test again.
Interesting! I found this issue difficult to reproduce in general, it seems to be erratic whether it happens or not.
Interesting! I found this issue difficult to reproduce in general, it seems to be erratic whether it happens or not.
The problem was pretty consistent on my device... I saw the continue tab perhaps 1 out of 20 times ....
My gut was telling me to look for a race condition where the server response was delayed... (My connection is over wireguard) ... This is why I'm not convinced it's fixed yet since dev builds are slower...
@lucbelliveau commented on GitHub (May 15, 2025):
> > Interesting! I found this issue difficult to reproduce in general, it seems to be erratic whether it happens or not.
The problem was pretty consistent on my device... I saw the continue tab perhaps 1 out of 20 times ....
My gut was telling me to look for a race condition where the server response was delayed... (My connection is over wireguard) ... This is why I'm not convinced it's fixed yet since dev builds are slower...
I believe this is a duplicate of #1570. Or rather that one is a duplicate of this. But I think I identified the underlying problem there. It just needs a proper fix...
@golinski commented on GitHub (May 23, 2025):
I believe this is a duplicate of #1570. Or rather that one is a duplicate of this. But I think I identified the underlying problem there. It just needs a proper fix...
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 @tali055 on GitHub (Feb 26, 2025).
What was the Problem?
This started with a recent app update, the tabs for continueing and currently listening in the Android Auto app are suddenly not showing up anymore, only the browse and downloads tabs are there.
Steps to Reproduce the Issue
What was Expected?
There used to be two tabs to the left of browse and downloads for the currently listening books where you could easily continue.
Phone Model
Samsung Galaxy A54
Phone OS
Android 14
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
Additional Notes
No response
@ttvAmavisca commented on GitHub (Mar 3, 2025):
for me this has been happening randomly for a long time. Sometimes it automatically continues las playing book, sometimes it shows continue listening and sometimes only browse and download appears. I have been trying to reproduce it consistendly but wasn't able. My first tought it was related to bad connection(since it normally hapens on the garage were the connection is usually poor) but i seem it happen also on cases with good connection so no idea why.
Phone Model
Pixel 8
Phone OS
Android 15
Audiobookshelf App Version
Android App - 0.9.79
Installation Source
Google Play Store
@tali055 commented on GitHub (Mar 3, 2025):
Interesting that it happens on- and off for you, it's constent for me since it started happening about a month ago, seems to not be (only) connection dependent then
@ttvAmavisca commented on GitHub (Mar 10, 2025):
Update:
You are right, it happens 100% of the time now.
In multy app(when you have for example google maps + audiobookshelf on the screen) you can only see the recomended on the audiobookshelft part. And if you open it in exclusive, only the library list and downloads shows up
Is there any guide on where to search for the part of the code that handles the android auto app? i may be able to help a bit(i am more of a low level programer but may surpass my hate to java/javascript to help with this XDD)
a quick search only finds ./android/app/src/main/res/xml/automotive_app_desc.xml that is obviusly not it
edit: nevermind, i am already into the vue hell :D
@Larryadd commented on GitHub (May 6, 2025):
Same issue here for a few months.
@lucbelliveau commented on GitHub (May 15, 2025):
I am also having this issue, I decided to take a look to see if I could fix it... I downloaded the latest release (v0.9.81-beta) a few weeks ago, and the problem continued.... So yesterday I cloned the repository, got myself ready to troubleshoot and found that I could not reproduce the issue.... (In fact this morning when I got in the car, I was pleasantly startled when my book resumed without any interaction from me!)
Either this issue has been fixed as of commit
cf2f684e80, or there is something about the development build that resolves the error... I'll wait until the next release build and test again.@tali055 commented on GitHub (May 15, 2025):
Interesting! I found this issue difficult to reproduce in general, it seems to be erratic whether it happens or not.
@lucbelliveau commented on GitHub (May 15, 2025):
The problem was pretty consistent on my device... I saw the continue tab perhaps 1 out of 20 times ....
My gut was telling me to look for a race condition where the server response was delayed... (My connection is over wireguard) ... This is why I'm not convinced it's fixed yet since dev builds are slower...
@golinski commented on GitHub (May 23, 2025):
I believe this is a duplicate of #1570. Or rather that one is a duplicate of this. But I think I identified the underlying problem there. It just needs a proper fix...
@advplyr commented on GitHub (May 23, 2025):
Agree, #1570 will be the main thread