AirenSoft / OvenPlayer

OvenPlayer is JavaScript-based LLHLS and WebRTC Player for OvenMediaEngine.
https://OvenMediaEngine.com/ovenplayer
MIT License
505 stars 125 forks source link

Not able to run the player in mobile browser but work fine in desktop #309

Closed chandan688 closed 7 months ago

chandan688 commented 1 year ago

Hi Team, we are getting an issue with player, when we implement the ads code then mobile browser player shows this error "media not ble to download"

Here is the url

https://publictv.in/PTV3.html

Only ads is working. Please fix this issue asap

chandan688 commented 1 year ago

any update on this?

SangwonOh commented 1 year ago

@chandan688 Hi. In our testbed, there seems to be no problem. Let us know what test environment is causing the problem. (For example, OS, OS version, Browser, Browser version etc...)

chandan688 commented 1 year ago

It's issue with chrome browser in mobile as well as in mobile mode under inspect element.

The issue is ads running but live streaming is not working with the ads tag. When we remove the adtag url then streaming / Player is working fine in both browser mode.

Here is the url https://publictv.in/PTV3.html

Screenshot_20221013_185211 Screenshot_20221013_185204

chandan688 commented 1 year ago

any update on this issue?

chandan688 commented 1 year ago

Any update on this. Am waiting for the solution.

getroot commented 1 year ago

@chandan688

I'm not a player developer, but since you keep pushing the OvenPlayer developer, so I took a look at this. (Don't push developers in the open source community. They may be very busy with other things and can lose motivation to run open source.)

The site you provide has a mixed content problem first. Could not load http streaming url from https page. You have to replace http://livestream.knowtable.xyz:5443/show/streams/Publictv_adaptive.m3u8 with https://livestream.knowtable.xyz:5443/show/streams/Publictv_adaptive.m3u8 .

SangwonOh commented 7 months ago

We are closing the issue due to a long period of inactivity. If further discussion is needed, please reopen the issue.