You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're seeing this on our crashlytics report in production:
Fatal Exception: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.get(ArrayList.java:437)
at com.google.android.exoplayer2.source.dash.DefaultDashChunkSource.updateManifest(DefaultDashChunkSource.java:282)
at com.google.android.exoplayer2.source.dash.DashMediaPeriod.updateManifest(DashMediaPeriod.java:182)
at com.google.android.exoplayer2.source.dash.DashMediaSource.processManifest(DashMediaSource.java:853)
at com.google.android.exoplayer2.source.dash.DashMediaSource.lambda$new$0(DashMediaSource.java:484)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.os.HandlerThread.run(HandlerThread.java:67)
Expected result
Even if the stream isn't correct, the application should not crash.
Actual result
The application crashes sometimes with the stack above
Media
We experienced it only on a low latency stream, I don't know if it's related.
Even if the stream isn't correct, the application should not crash.
I agree with that, we should ensure it get reported through the normal player error channels. I will update the code to capture this exception correctly.
The error itself looks like a representation got removed from an existing DASH period, which is indeed not allowed per spec. If you have any further details on the manifest itself and think it might be caused by something else, please let us know.
Activity
tonihei commentedon Oct 10, 2025
I agree with that, we should ensure it get reported through the normal player error channels. I will update the code to capture this exception correctly.
The error itself looks like a representation got removed from an existing DASH period, which is indeed not allowed per spec. If you have any further details on the manifest itself and think it might be caused by something else, please let us know.
Ensure errors during simulated manifest refresh do not crash app
Ensure errors during simulated manifest refresh do not crash app
Ensure errors during simulated manifest refresh do not crash app