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
8.10.3
Where did you get the app from
Other
Android version
14
Device model
Samsung S24 Ultra (SM-S928W)
First occurred
Has been happening for a few versions
Steps to reproduce
Start playing an episode.
Pause the episode and put Podcini in the background or close it.
Leave in the above state for a while. I don't know the exact amount of time when it will occur. It's usually in the background for me between 6hrs and up to 24hrs
Open Podcini and hit play on the "minimized" player. Icon will change from play to pause but the error in screenshot will appear and no playback starts
Expected behaviour
Open app after it being in background or closed and be able to hit play to resume playback.
Current behaviour
Icon will change from play to pause but the error in screenshot will appear and no playback starts
Yes, I've noticed this. The play button on the player control doesn't start the service, but the button at the episode on the list does. I will amend this later.
Checklist
App version
8.10.3
Where did you get the app from
Other
Android version
14
Device model
Samsung S24 Ultra (SM-S928W)
First occurred
Has been happening for a few versions
Steps to reproduce
Expected behaviour
Open app after it being in background or closed and be able to hit play to resume playback.
Current behaviour
Icon will change from play to pause but the error in screenshot will appear and no playback starts
Logs
full-logs.txt
The text was updated successfully, but these errors were encountered: