androidx / androidx/media

ForwardingPlayer that stops events gets MediaController out of sync

Open
#163 4 comments 0 reactions 1 assignee View on GitHub

@marcbaechinger is already working on this.

Since Sep 6, 2022.

enhancement
Dominant language
Java
Stars
3k
Forks
955
Avg merge
12d 14h
Merged PRs (30d)
2

Description

Media3 Version

1.0.0-beta02

Devices that reproduce the issue

Emulator

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Not tested

Reproduction steps

Use the horologist media-sample.

MediaController -> MediaSession -> WearConfiguredPlayer -> ExoPlayer.

WearConfiguredPlayer will open the Bluetooth fragment if no headphones are connected, ignoring the play() command.
If you close the fragment without selecting headphones, you end up on the player screen. Hitting play again will open the fragment again. After closing the fragment again, the player State is out of sync.

Workaround is to fire an event - see PR in https://github.com/google/horologist/pull/558/files

Expected result

MediaController - playWhenReady = true
ExoPlayer - playWhenReady = false

Actual result

MediaController - playWhenReady = false
ExoPlayer - playWhenReady = false

Media

Uamp content in media-sample

Bug Report
  • You will email the zip file produced by adb bugreport to dev.exoplayer@gmail.com after filing this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.