[Bug]: Next item in Playlist not started automatically #1092

New Issue

2026-04-24T23:48:20+02:00

adam commented

2026-04-24 23:48:20 +02:00

Originally created by @realredknight on GitHub (Nov 24, 2024).

What was the Problem?

When a playlist is played and one item is finished, the playlist stays in the state "Playing" while the player Screen shows "paused". The playlist enters a state where neither a new item is played nor the icon to tap "play" is shown.

The App needs to be killed and started again to advance to the next item.

Steps to Reproduce the Issue

Add items to a playlist
play first item
wait until item1 has finished playing

What was Expected?

after reaching the end of "item 1", expected behaviour is to play "item 2" without interaction.

Phone Model

Fairphone 3+

Phone OS

Android 13

Audiobookshelf App Version

Android App - 0.9.77

Installation Source

Google Play Store

Additional Notes

No response

Originally created by @realredknight on GitHub (Nov 24, 2024). ### What was the Problem? When a playlist is played and one item is finished, the playlist stays in the state "Playing" while the player Screen shows "paused". The playlist enters a state where neither a new item is played nor the icon to tap "play" is shown. The App needs to be killed and started again to advance to the next item. ![grafik](https://github.com/user-attachments/assets/9ba1fb05-e5d9-4bbc-9470-f0bc638c3e4c) ### Steps to Reproduce the Issue 1. Add items to a playlist 2. play first item 3. wait until item1 has finished playing ### What was Expected? after reaching the end of "item 1", expected behaviour is to play "item 2" without interaction. ### Phone Model Fairphone 3+ ### Phone OS Android 13 ### Audiobookshelf App Version Android App - 0.9.77 ### Installation Source Google Play Store ### Additional Notes _No response_

adam added the bug label 2026-04-24 23:48:20 +02:00

adam closed this issue

2026-04-24 23:48:20 +02:00

adam commented

2026-04-24 23:48:21 +02:00

@ZLoth commented on GitHub (Nov 27, 2024):

I'm able to replicate this issue. The expectation is that the next title in the playlist is played, not stopped.

https://github.com/user-attachments/assets/7f785a5f-ccba-4d2e-b6f9-93e081101a8e

@ZLoth commented on GitHub (Nov 27, 2024): I'm able to replicate this issue. The expectation is that the next title in the playlist is played, not stopped. https://github.com/user-attachments/assets/7f785a5f-ccba-4d2e-b6f9-93e081101a8e

adam commented

2026-04-24 23:48:22 +02:00

@Pittermaennchen commented on GitHub (Jan 5, 2025):

Same here. Can't use the audiobookshelf app because of this. :(

@Pittermaennchen commented on GitHub (Jan 5, 2025): Same here. Can't use the audiobookshelf app because of this. :(

adam commented

2026-04-24 23:48:22 +02:00

@Pittermaennchen commented on GitHub (Jan 12, 2025):

Can anyone help with this? Otherwise the audiobookshelf-app is pretty useless in daily life. :(

@Pittermaennchen commented on GitHub (Jan 12, 2025): Can anyone help with this? Otherwise the audiobookshelf-app is pretty useless in daily life. :(

adam commented

2026-04-24 23:48:23 +02:00

@nichwall commented on GitHub (Jan 12, 2025):

This is related to https://github.com/advplyr/audiobookshelf-app/issues/416

Auto advancing to the next item has not been implemented in the apps yet.

@nichwall commented on GitHub (Jan 12, 2025): This is related to https://github.com/advplyr/audiobookshelf-app/issues/416 Auto advancing to the next item has not been implemented in the apps yet.

adam commented

2026-04-24 23:48:23 +02:00

@realredknight commented on GitHub (Jan 13, 2025):

This is related to #416

Auto advancing to the next item has not been implemented in the apps yet.

The "expected Behaviour"-Part is related to (or the same as) #416

Still, if you look on top of my provided Screenshot, there remains a bug in the current implementation, where player state is "Stop" (as the current item is finished) but the button state is still "playing".

It feels like a race condition here, as the app does not accept any further input and must be killed via System --> Apps and re-opened again to start a new item manually

@realredknight commented on GitHub (Jan 13, 2025): > This is related to #416 > > Auto advancing to the next item has not been implemented in the apps yet. The "expected Behaviour"-Part is related to (or the same as) #416 Still, if you look on top of my provided Screenshot, there remains a bug in the current implementation, where player state is "Stop" (as the current item is finished) but the button state is still "playing". It feels like a race condition here, as the app does not accept any further input and must be killed via System --> Apps and re-opened again to start a new item manually

adam commented

2026-04-24 23:48:23 +02:00

@github-actions[bot] commented on GitHub (Jan 27, 2025):

Fixed in v0.9.79-beta.

@github-actions[bot] commented on GitHub (Jan 27, 2025): Fixed in [v0.9.79-beta](https://github.com/advplyr/audiobookshelf-app/releases/tag/v0.9.79-beta).

adam commented

2026-04-24 23:48:24 +02:00

@advplyr commented on GitHub (Jan 27, 2025):

Note this only addressed the play button issue. The other issue is #416

@advplyr commented on GitHub (Jan 27, 2025): Note this only addressed the play button issue. The other issue is #416

adam commented

2026-04-24 23:48:24 +02:00

@ZLoth commented on GitHub (Jan 27, 2025):

Thank you @advplyr . Looking forward to the actual release.

@ZLoth commented on GitHub (Jan 27, 2025): Thank you @advplyr . Looking forward to the actual release.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/audiobookshelf-app#1092