You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've run into an issue where version 1.6.0 of the plugin gives an error on playing a video: media could not be loaded because the server or network failed or because the format is not supported.
The device this occurs on runs Chrome version 64 and Android System Webview version 64
On testing, a similar device with Chrome version 74 and ASW version 80 does not have this issue, which leads me to think some property of Chrome 64 is causing this.
I am aware these are outdated versions, but unfortunately upgrading the devices is a difficult process in our organisation.
We're using version 1.6.0 of the plugin.
Is there an indication of the minimum requirements for each version of this plugin? Would it help to upgrade or downgrade to be compatible with older versions of Chrome again?
The text was updated successfully, but these errors were encountered:
It may be a content security policy restriction. I ran into something similar and had to add 'blob:' to the media-src or worker-src. Can't recall which one.
We've run into an issue where version 1.6.0 of the plugin gives an error on playing a video:
media could not be loaded because the server or network failed or because the format is not supported.
The device this occurs on runs Chrome version 64 and Android System Webview version 64
On testing, a similar device with Chrome version 74 and ASW version 80 does not have this issue, which leads me to think some property of Chrome 64 is causing this.
I am aware these are outdated versions, but unfortunately upgrading the devices is a difficult process in our organisation.
We're using version 1.6.0 of the plugin.
Is there an indication of the minimum requirements for each version of this plugin? Would it help to upgrade or downgrade to be compatible with older versions of Chrome again?
The text was updated successfully, but these errors were encountered: