-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
console errors when using component for twitch stream #358
Comments
Same with Vimeo direct URL's. Reverting back to |
@pedropcruz @hellojere What URL/props are you using to cause this error? Examples code/repos/jsFiddles are very useful. |
@cookpete Happens with the react-player demo too when using the following for the source:
|
@cookpete in my case just showing doing this: <ReactPlayer className="react-player" url="https://www.twitch.tv/pedropcruz"
config={{
twitch:{
options:{
'font-size':'small',
channel: 'pedropcruz',
chat: 'default',
layout: 'video-and-chat',
theme: 'dark',
src: 'https://www.twitch.tv/pedropcruz/chat'
}
}
}}
/> |
@pedropcruz your config is working correctly for me? See jsFiddle. After a closer look at your screenshot, it looks like it could be an adblock extension that is preventing @hellojere this looks like a separate issue where the Vimeo player is attempting to play your MP4 file, as the URL for the file contains |
@cookpete Hmmn. Ok. It indeed should be playing an MP4 and not embedding a Vimeo player at all - it's a direct file URL provided by Vimeo Pro. I'll look into other solutions for this. Cheers. |
nop @cookpete already remove adblock and other type of that extension, and the error continues the same. |
@pedropcruz What are the exact console errors you are seeing with adblock disabled? |
Just had a closer look – you guys are trying to use options for the Embed Everything player like I'll see if it makes sense to switch over to use |
Turns out that |
Hello there,
I' m trying to put my component with url and with some options on twitch, and have this error:
How i can solve this? Many thanks!
The text was updated successfully, but these errors were encountered: