starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: Impossible listening duration (>24 hours) #2885

New Issue
Closed
opened 2026-04-25 00:11:35 +02:00 by adam · 4 comments
adam commented 2026-04-25 00:11:35 +02:00
Owner
Copy Link
Copy Source

Originally created by @FiendFEARing on GitHub (Jul 13, 2025).

What happened?

Image Image

What did you expect to happen?

It's impossible for me to listen for that long.

Steps to reproduce the issue

I'm not sure what happened.

Audiobookshelf version

v2.25.1

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

macOS

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs

I can provide you with the log files for those two days separately.

Additional Notes

No response

Originally created by @FiendFEARing on GitHub (Jul 13, 2025). ### What happened? <img width="883" height="248" alt="Image" src="https://github.com/user-attachments/assets/9629a982-1250-402f-ac50-2b1f0fd84a8e" /> <img width="856" height="267" alt="Image" src="https://github.com/user-attachments/assets/1a922988-18ad-4c04-99df-5830ef1e4df1" /> ### What did you expect to happen? It's impossible for me to listen for that long. ### Steps to reproduce the issue I'm not sure what happened. ### Audiobookshelf version v2.25.1 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? macOS ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs I can provide you with the log files for those two days separately. ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:11:35 +02:00
adam closed this issue 2026-04-25 00:11:35 +02:00
adam commented 2026-04-25 00:11:35 +02:00
Author
Owner
Copy Link
Copy Source

@Vito0912 commented on GitHub (Jul 13, 2025):

This is the result of some sync bugs reported in the app repository and here. It is not related to the heatmap, but to your actual listening session, which has a too long listening duration added to it. This mainly happens with the official apps have some bugs that can unfortunately cause this (espeically if the app is in the background a long time and then continued without properly closing the session).

You can delete the session in the session overview to correct it again.

To prevent this in the future, please properly close the session before closing the app.

I am also sure this is a duplicate issue, but I currenctly can't find it

@Vito0912 commented on GitHub (Jul 13, 2025): This is the result of some sync bugs reported in the app repository and here. It is not related to the heatmap, but to your actual listening session, which has a too long listening duration added to it. This mainly happens with the official apps have some bugs that can unfortunately cause this (espeically if the app is in the background a long time and then continued without properly closing the session). You can delete the session in the session overview to correct it again. To prevent this in the future, please properly close the session before closing the app. I am also sure this is a duplicate issue, but I currenctly can't find it
adam commented 2026-04-25 00:11:35 +02:00
Author
Owner
Copy Link
Copy Source

@FiendFEARing commented on GitHub (Jul 13, 2025):

This is the result of some sync bugs reported in the app repository and here. It is not related to the heatmap, but to your actual listening session, which has a too long listening duration added to it. This mainly happens with the official apps have some bugs that can unfortunately cause this (espeically if the app is in the background a long time and then continued without properly closing the session).

You can delete the session in the session overview to correct it again.

To prevent this in the future, please properly close the session before closing the app.

I am also sure this is a duplicate issue, but I currenctly can't find it

Okay, I do often experience issues with sessions not closing properly.
After the Android official ABS app has been running in the background for a long time, it sometimes fails to sync playback progress (an exclamation mark ❗ appears on the album cover), and the logs show repeated progress sync failures.
That may be the cause.

Image Image
@FiendFEARing commented on GitHub (Jul 13, 2025): > This is the result of some sync bugs reported in the app repository and here. It is not related to the heatmap, but to your actual listening session, which has a too long listening duration added to it. This mainly happens with the official apps have some bugs that can unfortunately cause this (espeically if the app is in the background a long time and then continued without properly closing the session). > > You can delete the session in the session overview to correct it again. > > To prevent this in the future, please properly close the session before closing the app. > > I am also sure this is a duplicate issue, but I currenctly can't find it Okay, I do often experience issues with sessions not closing properly. After the Android official ABS app has been running in the background for a long time, it sometimes fails to sync playback progress (an exclamation mark ❗ appears on the album cover), and the logs show repeated progress sync failures. That may be the cause. <img width="365" height="196" alt="Image" src="https://github.com/user-attachments/assets/f95b90e3-5898-4971-a2a6-54ac8b01c1b3" /> <img width="383" height="183" alt="Image" src="https://github.com/user-attachments/assets/3bded910-e87e-4dfe-a93d-5dbb6023765b" />
adam commented 2026-04-25 00:11:35 +02:00
Author
Owner
Copy Link
Copy Source

@FiendFEARing commented on GitHub (Jul 14, 2025):

This is the result of some sync bugs reported in the app repository and here. It is not related to the heatmap, but to your actual listening session, which has a too long listening duration added to it. This mainly happens with the official apps have some bugs that can unfortunately cause this (espeically if the app is in the background a long time and then continued without properly closing the session).

You can delete the session in the session overview to correct it again.

To prevent this in the future, please properly close the session before closing the app.

I am also sure this is a duplicate issue, but I currenctly can't find it

Today, after using a third-party app, I noticed an even more bizarre issue that doesn’t seem to be explainable by an improperly closed session alone: In Listening Sessions, the Time Listened value actually showed up as a negative number.

Image Image Image
@FiendFEARing commented on GitHub (Jul 14, 2025): > This is the result of some sync bugs reported in the app repository and here. It is not related to the heatmap, but to your actual listening session, which has a too long listening duration added to it. This mainly happens with the official apps have some bugs that can unfortunately cause this (espeically if the app is in the background a long time and then continued without properly closing the session). > > You can delete the session in the session overview to correct it again. > > To prevent this in the future, please properly close the session before closing the app. > > I am also sure this is a duplicate issue, but I currenctly can't find it Today, after using a third-party app, I noticed an even more bizarre issue that doesn’t seem to be explainable by an improperly closed session alone: In Listening Sessions, the Time Listened value actually showed up as a negative number. <img width="430" height="251" alt="Image" src="https://github.com/user-attachments/assets/c9f34e5b-3f9c-45f9-a8e0-5edca37799f3" /> <img width="280" height="311" alt="Image" src="https://github.com/user-attachments/assets/9aa435f6-2263-4146-8826-7f2858c3a489" /> <img width="875" height="142" alt="Image" src="https://github.com/user-attachments/assets/39e3d392-25ab-474a-89e2-2d7634b13c14" />
adam commented 2026-04-25 00:11:35 +02:00
Author
Owner
Copy Link
Copy Source

@Vito0912 commented on GitHub (Jul 14, 2025):

Anything reported by third party apps is not an issue with ABS. While ABS could prohibit negative numbers it would not fix the cause (the third party app).

Idk how these apps do it, but I know it can be prevented as I built an client myself and while using never had any such extremes.

@Vito0912 commented on GitHub (Jul 14, 2025): Anything reported by third party apps is not an issue with ABS. While ABS could prohibit negative numbers it would not fix the cause (the third party app). Idk how these apps do it, but I know it can be prevented as I built an client myself and while using never had any such extremes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2885
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?