-
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
Crash on Android 5.1 when try to release player #7954
Comments
Please provide complete information as requested in the issue template. The issue template can be found here. If you're unable to share bug reports or test content publicly, please send them to dev.exoplayer@gmail.com using a subject in the format "Issue #1234", where "#1234" should be replaced with your issue number. Please also update this issue to indicate you’ve done this. The parts in particular that we really need is a bug report captured using adb, as well as a link to some test content. |
This is normally caused by some kind of build issue, rather than being a problem with the library. Forgetting to enable Java 8 support is a common cause, so it's definitely worth checking this. It's also possible that you're using overly aggressive code stripping / Proguard configuration. |
Thank you for your answer @ojw28. But I provide log from debug version of my app. For this reason it can't be proguard configuration. Of cause I use Java 8 for my app :) I'll try to delete gradle cache. May be it helps... |
I can confirm this issue. I upgraded to 2.12.0 last week and got crashes from the field. |
@boylenssen - If that's the case then please provide detailed reproduction steps. For example, a small sample project that reproduces the issue, along with steps necessary to get to the point where the emulator crashes when using it. Note that we have been unable to reproduce the issue internally. We don't see the issue occurring for Google owned apps, which obviously have fairly wide usage. There are also only limited reports of the issue affecting external developers. This is pretty strong evidence to suggest that it's not as straightforward as just being an issue with 2.12.0, and is more likely to be something specific (and probably unusual) about the way your particular app(s) are being built. |
Hey @WagesOfSin. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Since there haven't been any recent updates here, I am going to close this issue. @WagesOfSin if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this. |
I think this issue is caused by guava, it's been reported in related issues, but I'm adding my fix here too.
|
[REQUIRED] Issue description
Updated on the latest version 2.12.0 and I have crash on Android 5, Android 6 when I try to release the player. Don't have this crash on version 2.11.8. I can't reproduce this issue on your demo app.
[REQUIRED] Reproduction steps
[REQUIRED] Link to test content
It doesn't mater
[REQUIRED] A full bug report captured from the device
[REQUIRED] Version of ExoPlayer being used
Version is 2.12.0
[REQUIRED] Device(s) and version(s) of Android being used
Lyf Wind 7 Black LS-5016 Android 6.0.1
Vivo Y21 Android 5.1.1
The text was updated successfully, but these errors were encountered: