1.9.0 CastPlayer goes into an idle state when starting new items while casting.
@marcbaechinger is already working on this.
Since Jan 14, 2026.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Version
Media3 1.9.0
More version details
Changing the current playing item while already casting causes the player to go into an idle state with no items or playing status while the selected item plays on the cast device.
The player can eventually update with an EVENT_MEDIA_METADATA_CHANGED update or forcing it by moving to the next item in the playlist.
Devices that reproduce the issue
Pixel 9a - 16
Galaxy Z Flip5 - 16
Lenovo Tab M7(TB-7306F) - 11
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
- Open demo-session
- Play track from artist screen
- Observe playing locally on PlayerActivity
- Go back
- Start casting session while still playing
- Observe playing on cast device
- Play another track from the artist screen
- Observe PlayerActivity stuck in "Connecting..." state
- If not in connecting state, go back and select another track.
Expected result
When a user selects a new track it should update in the app's UI and show notification consistently.
Actual result
When a user selects a new track it does not update in the app's UI or show notification immediately.
Media
https://github.com/user-attachments/assets/2aaddda8-cf70-4782-a8a4-12b081431e19
Bug Report
- You will email the zip file produced by
adb bugreportto android-media-github@google.com after filing this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.