Hi
On the release notes it says that the videoplayer will work on these too. Considering how simple it is to make for android: you can see EasyVideo asset for proof because it includes the source code, and I wrote a java plugin with 7 lines of code that runs the video on a texture too. I’m lost as to why it’s not on 5.6beta 7 yet
any updates on this? I would love to remove all my plugins so I can clean up my code. Also Tizen, I would hate to have to write a plugin for Tizen just for this.
Yeah, missing Android support ruins the whole idea of VideoPlayer feature in 5.6
The devs are working hard on the integration of proper Android support within the Beta cycle. And I can assure you it is not a trivial task, otherwise the problem would have been fixed by now, given the importance of the subject matter.
Almost everything is not a trivial task on android 
Can we hope for android support in 5.6 release or it will be delayed to 5.7?
5.6 is still the target version.
Well, I differ on that opinion. It took me a few hours to write a video player for android that runs on Unity and most of the time was spent learning how to communicate Unity with the jar file.
In any case as long as this is on 5.6 i’m happy, specially if it also includes Tizen because I don’t want to have to rewrite all code from android to tizen and learn a new communication mechanism and all that stuff just for me to have to delete the plugin in a month.
@LeonhardP I have a problem on Android platform. I have a video picker that allows to select a video and then play it on Unity with VideoPlayer but I get an error:
Can’t play movie [content://com.android.providers.media.documents/document/video%3A101120]
Reading documentation it says: https://docs.unity3d.com/560/Documentation/ScriptReference/Video.VideoPlayer-url.html
File URLs are filesystem paths that are either absolute on the platform or relative to the player root.
In case of Android it should be opened on your side with: context.getContentResolver().openInputStream(uri);
I don’t know how you handle this but it should be supported because Android uses content resolvers and it’s the correct way.
Reported with Case 880381
@bdovaz there is no mention in the documentation that we support content providers.
We will consider adding it as a feature in one of the future releases.
There is no mention because we all understand that is the right thing to do, it’s how Android file system API works.
OK, I will wait to that release.