You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used the search function for OPEN issues to see if someone else has already submitted the same bug report.
I have also used the search function for CLOSED issues to see if the problem is already solved and just waiting to be released.
I will describe the problem with as much detail as possible.
If the bug only to occurs with a certain podcast, I will include the URL of that podcast.
App version
6.5.9
Where did you get the app from
Other
Android version
14
Device model
Samsung
First occurred
recently
Steps to reproduce
Play an episode in queue,
put Podcini in background or turn off screen,
when the next episode in queue starts, notification panel likely not show up,
this is when ForegroundServiceStartNotAllowedException shows in Logcat,
Podcini may keep playing, or may get stopped by the system sometime later.
Since Google can't resolve this issue for over 2 years, I don't expect that they be able to do it soon. So from now on the workaround is to build apk's with target SDK set to 30 (Android 11), though build and tests will be with the most recent SDK's and Android versions (for now SDK 35 and Android 14).
Checklist
App version
6.5.9
Where did you get the app from
Other
Android version
14
Device model
Samsung
First occurred
recently
Steps to reproduce
Play an episode in queue,
put Podcini in background or turn off screen,
when the next episode in queue starts, notification panel likely not show up,
this is when ForegroundServiceStartNotAllowedException shows in Logcat,
Podcini may keep playing, or may get stopped by the system sometime later.
This is noticed on Samsung Android 14 devices.
This relates to long-standing issues reported to media3: androidx/media#111
and to Android: https://issuetracker.google.com/issues/307329994
Expected behaviour
No response
Current behaviour
No response
Logs
No response
The text was updated successfully, but these errors were encountered: