Automattic / Automattic/pocket-casts-android

Podcast was playing even though the UI said it wasn't, and the audio doubled-up when I pressed play

Open
#2,123 0 comments 0 reactions 0 assignees View on GitHub
[Area] Playback [Priority] Low [Type] Bug
Dominant language
Kotlin
Stars
2.8k
Forks
308
Avg merge
1d 13h
Merged PRs (30d)
143

Description

### Description

I launched the app (I believe it was no longer in memory by that point) , and pressed play on the currently in-progress episode, which was not downloaded, but was being streamed. After a few seconds it hadn't started playing yet, so I pressed the play button again (it may have said it was playing already, in which case I presumably tapped twice, once to pause and once to play again).

I'm don't remember the exact timing of everything or exactly what I pressed when, but the app ended up playing two instances of the episode, offset a bit from each other. Pressing pause would pause one instance while the other kept playing. The playback controls in the notification shade behaved the same way as the ones in the app. To fix this state, I had to swipe away the app from the app switcher.

### Step-by-step reproduction instructions

I don't have easily reproducible steps, unfortunately

### Screenshots or screen recording

https://github.com/Automattic/pocket-casts-android/assets/10224994/bfe17141-4e26-46eb-9494-509a416b0800

### Did you search for existing bug reports?

- [X] I have searched for existing bug reports.

### Device, Operating system, and Pocket Casts app version

Pixel 6, Android 14, Pocket Casts 7.62-rc-5 (9218)

Contributor guide

Open the contributing guide

Research direction

Start by investigating playback after launching the app with a non-downloaded episode, then pressing play repeatedly while streaming. Compare the in-app and notification-shade controls; done means one playback instance remains active and pause controls stop it consistently.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.