-
Notifications
You must be signed in to change notification settings - Fork 245
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
Black screen orientation issues in 5.0.3 on Android, No implementation found on iOS #177
Comments
can you share that part of code with us? |
Sure, I've attached my widget code below. For context, I use a modified version of
When I rotate, this message shows up. Sometimes when I rotate, it goes black and resolves itself quickly. Other times, it doesn't ever return to having picture.
On iOS, even if I make the very root widget |
hmmmm, Also, i should mention that this package is based on platform view but video_player isn't. Thus, i guess you cannot easily migrate all features of the video_player dependent packages like chewie to vlc. |
Here is my repo I'm working with, should work on a fresh clone and a Truth be told, all I did was convert from using I do think it's a bit naive but on Android, everything seems to work -- except for that black screen orientation issue. I'm motivated to properly make the switch to this plugin as some Matroska videos don't work with |
Hi, I just discovered that using So I find this to be a workable less than inelegant solution -- a bit better than the player going black forever. |
I checked your migrated chewie code on a sample app. For me, there is lots of errors in console when i enter to and exit from fullscreen mode multiple times. Also, i suggest you do not copy the source code of each project in your app. Just fork it and modify parts of code you want. After that you can include your modified fork in the project. it's a lot easier for someone to read, test and compare the code with the main git library. Also, if there is an update in the library, it might be easier to compare & merge the changes with your modified fork. I'm still looking for a solution. |
I'm not sure how much of a help it is, but I can say that the issue does not lie with the modified version of Here's the error that pops up in my console when I try to play a video on iOS (both simulator and physical device):
When running this on Android simulator (I don't have a physical device to test), I get the following error on initialization:
I can also provide the code that I am using that reproduces this issue here Hopefully this helps to narrow down issues! |
yea, i checked your repo. you must not call the initialize method right after creating controller because the platform view is not ready yet. if you wanna initialize manually, you have to wait for a variable "isReadyToInitialize" to be set true. |
I managed to migrate from using
video_player
to using this, but I'm having issues on Android where if the orientation changes I get a black screen which I checked around was supposedly fixed in 4.0.0, I'm facing the same issue in 5.0.3 (related to #103 and #104).The black screen issue seems to be fixed on seek, so to fix that I'm thinking about doing a function that responds to orientation to seek to the current duration.This doesn't seem to be elegant, I'm trying to maximize the size of aVlcPlayer
to be as big as the screen allows with aSizedBox.expand
.EDIT: It appears this issue does indeed only happen when I use a
SizedBox.expand
. Is there any way to get the behavior I want without the black screen issue without this? It seems that otherwise in landscape, the video would be very small.I'm also unable to play videos on iOS and I'm getting this issue:
Seems to be a widget issue on my end. I was able to play an MP4 with this, but not an MKV. Is this plugin unable to do Matroska on iOS? I was under the impression it should as VLC plays Matroska files.No implementation found for method listen on channel flutter_video_plugin/getVideoEvents_null
Any fixes? I would really like to fully migrate my project to use this.
The text was updated successfully, but these errors were encountered: