Video Player Controller network from 0.4.1 won't work

[vijaykanta]

I recently upgraded video player from default to 0.4.1 to allow VideoPlayerController.network() constructor to work out of the box. The sample code was straightly taken from the video player plugin website, where the URL is passed for streaming and it won't work. I see a dark box when I initiate playing.

Here's the log

V/MediaPlayer-JNI( 6863): native_setup
V/MediaPlayer( 6863): constructor
V/MediaPlayer( 6863): setListener
V/MediaPlayer( 6863): setVideoSurfaceTexture
V/MediaPlayer-JNI( 6863): setParameter: key 1400
V/MediaPlayer( 6863): MediaPlayer::setParameter(1400)
V/MediaPlayer-JNI( 6863): setAudioStreamType: 3
V/MediaPlayer( 6863): MediaPlayer::setAudioStreamType
V/MediaPlayer( 6863): setVideoSurfaceTexture
V/MediaPlayer( 6863): prepareAsync
D/MediaHTTPConnection( 6863): setReadTimeOut = 30000ms
D/MediaHTTPConnection( 6863): setReadTimeout with 30000ms
I/System.out( 6863): (HTTPLog)-Static: isSBSettingEnabled false
I/System.out( 6863): (HTTPLog)-Static: isSBSettingEnabled false
W/MediaHTTPConnection( 6863): request failed with error => 0
D/MediaHTTPConnection( 6863): setReadTimeout with 30000ms
I/System.out( 6863): (HTTPLog)-Static: isSBSettingEnabled false
I/System.out( 6863): (HTTPLog)-Static: isSBSettingEnabled false
W/MediaHTTPConnection( 6863): request failed with error => 0
V/MediaPlayer( 6863): message received msg=100, ext1=1, ext2=-1005
E/MediaPlayer( 6863): error (1, -1005)
V/MediaPlayer( 6863): callback application
V/MediaPlayer( 6863): back from callback
E/MediaPlayer( 6863): Error (1,-1005)

However the VideoPlayerController.asset() works flawlessly with physical video.

[vijaykanta]

Bump. Can anyone find a solution for me here?

[vijaykanta]

Ok guys, sorry, but the URL I was using to load off network was a dead link. I have used a different link and it works out of the box immediately. It's all in the game of patience and research. :D

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.