-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Android 7.1.1 Nougat (API 25) ABI x86_64 not playing Video #672
Comments
this is a problem i am facing! actually the app freezes for sometime before playing the video. but then it starts |
them again it starts playing!!! anyone knows why its skipping? |
this solves while using exoplayer |
@michaelspeed I also solved by using exoplayer, but now I cannot see the video, just a black window, and from my log I have com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 401. Did you got the same? |
well sometimes it works and sometimes i get the same error with a black screen. i checked it with ios version and no issues there |
Using ExoPlayer solves my problem guys. I don't see any black windows. Want to share your code? |
@a-koka I'm using clojurescript, but if you want I can share it.. However my code works fine by using react-navive-video without exoplayer, just the app freeze before show the video (but at the least I can see the video).
build.grandle
Is it right? |
This is how my
I haven't tried your approach of renaming the project but I can't image why it would work any different. I'm not having any issues with a black screen though. Did you implement the hack to update Here's a snippet of how to hack
|
@a-koka For now I didn't implemented the onLoad callback.. but I think my problem is about cookies because I got this response com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 401. .I opened this issue #683 |
ExoPlayer cookie support will be included in 2.2.0 |
Videos aren't playing on Android Nougat (API 25) ABI x86_64. Could this be an issue across all 64-bit ABIs?
The text was updated successfully, but these errors were encountered: