Automattic / Automattic/pocket-casts-android
Conflicting Play States Shown in App
- Dominant language
- Kotlin
- Stars
- 2.8k
- Forks
- 308
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 143
Description
A user reported that the app shows the episode is paused in the app, but then if you open up the Now Playing screen it shows as playing. The episode is actually paused at the time.
> Below is a video of a bug that happens quite often. I think it happens after stopping a podcast via Bluetooth speakers/earbuds, then opening the app at a later stage. Once the app is opened, it appears as if the podcast is playing but it isn't.
I was able to reproduce this _once_ with a pre-release 7.20 build, but the bug does not appear consistently for me. I used these steps.
1. Connect to bluetooth
2. Begin playing a podcast by tapping play on the miniplayer
3. (maybe, I can't remember if I did this for certain) Swipe Pocket Casts away from the app switcher
4. Pause playback from the Bluetooth device
5. Open Pocket Casts
6. Observe that the miniplayer shows the podcast is playing even though it is paused.
Contributor guide
Research direction
Start with the Bluetooth reproduction steps in the issue, including dismissing the app, pausing from the Bluetooth device, and reopening Pocket Casts. Compare the miniplayer and Now Playing screen with the actual paused state; done means both screens consistently show the episode as paused after this sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100