getting ERROR_CODE_DECODING_FAILED when the adaptative jump from 512x288@25fps to 704x396@50fps

Version

ExoPlayer 2.19.1

More version details

Tag version Exoplayer 2.19.1

Devices that reproduce the issue

Galaxy S22 Ultra Android 13

Devices that do not reproduce the issue

Redmi Note 12 Pro+

Reproducible in the demo app?

Yes

Reproduction steps

1. open an adaptative dash stream as normally done on exoplayer demo with the particularity that 512x288@25fps and 704x396@50fps are one of the tracks
2. check the debugtextview to be sure that it is starting with the 512x288@25fps
3. wait few seconds until the track selected is 704x396@50fps
4. observe the error in the logs and the error message displayed to the client
5. click the select tracks button without exiting the player
6. select the 704x396@50fps and hit play
7. check that in this case no error is returned, so the device is able to play 704x396@50fps
8. go back to auto in a way that the player start from 512x288@25fps and the point 3 will happen again

Expected result

1. the device is able to play 704x396@50fps when selected manually. Should be able to do the same also when in AUTO mode.

2. The app or the player should recover from the ERROR_CODE_DECODING_FAILED removing that particular track from the automatic track selection and resume normally. Only when there are no more compatible track available it should send the error to the user

Actual result

The player stop showing the Playback Failed message to the user

Media

no demo url will fit with the error because there is no stream with this particular tracks:

• 512x288@25fps
• 704x396@50fps
  we will send a clear media url via email that has the issue
  UPDATE: we sent the email. If you need any adjustments to the manifest order, please don't hesitate to ask.

Bug Report

• You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.