ExoPlayer 2.19.1 is processing ad metadata when playWhenReady is false.
@marcbaechinger is already working on this.
Since Nov 14, 2023.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
I am in the process of updating an app from ExoPlayer 2.15.1 to 2.19.1.
The streams we are using have ad metadata at the very beginning of them. The app relies on a 3rd party sdk for its live streams and ad management and that sdk needs to be initialized fully before metadata can be processed. In 2.15.1 we achieved this by setting playWhenReady to false until the 3rd party SDK was ready. Once the sdk is ready, we set ExoPlayer.playWhenReady to true and then we see the ad metadata be processed. However, in 2.19.1, even after setting ExoPlayer.playWhenReady to false, we are seeing metadata being processed. Is this expected? If it is, is there a way to stop metadata processing in ExoPlayer 2.19.1?
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.