-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random crashes in IMA #8290
Comments
Crash 1 should go away if you upgrade to 2.12 as we now silence the unexpected error from this case, but the root cause it uncertain: it seems we think an ad isn't playing when the IMA SDK notifies For crash 2 I'm making a fix to turn this unexpected case into a warning, which will go into the next release. Thanks for reporting these issues. If you have any statistics on the relative frequency of the errors it would be helpful if you could share that information so we can decide whether it's worth digging into the causes (as opposed to just suppressing the errors). |
I'll provide the details as we work with @chladto1 on the same projects. The numbers are actually fairly low, approximately 0.15% of playback sessions are affected by these exceptions, but they are constantly present in the statistics. |
It's intended to log a warning in this case, rather than throw. Issue: #8290 #minor-release PiperOrigin-RevId: 347790527
Thanks for the information. From the next release both errors should be handled by skipping ad playback. Hopefully this is okay for the time being given these are occurring at a low volume. Longer term it would be good to try to figure out why the unexpected cases are happening. I will plan to discuss with the IMA SDK team what the possible cause could be, and whether we have options for reporting back these non-fatal errors so we can try to eliminate them over time. |
It's intended to log a warning in this case, rather than throw. Issue: #8290 PiperOrigin-RevId: 347790527
Issue description
Could you please take a look at these logs? These are crashes from Firebase, we do not have any context but hopefully you will found some issue to fix.
Reproduction steps
Unknown
Link to test content
Unknown
A full bug report captured from the device
Crash 1
Crash 2
Version of ExoPlayer being used
2.11.8
Device(s) and version(s) of Android being used
Device and OS independent
The text was updated successfully, but these errors were encountered: