-
Notifications
You must be signed in to change notification settings - Fork 49
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
Cross domain Exception #118
Comments
Yep get this as well for our Pro account! |
Hello, I have the same problem. Did you solve this? |
Did you manage to solve this? |
Unfortunately, nope. Nada |
I chased Vimeo support. Part of my message to them:
And this is Vimeo's official response:
|
If you are using AVPRO make sure you select adaptive resolution and for the vimeo token, do not generate it from "Get Token" button because you will get CORS issue. Instead go to https://developer.vimeo.com/ and create a new app, and then you can generate a API token and insert it into Unity. This will fix the CORS issue and you will be able to play the videos from Webgl. Make sure to setup AVPRO (hls.js or dash.js) If you are not using AVPRO then you will not be able to play the videos on Webgl because Unity Media player does not support adaptive resolution. If you don't select adaptive resolution vimeo will not return .m3u8 (hls.js) or .mpd (dash.js) and you will get playback error. |
I'm having troubles playing private videos on my WebGL deploy. I have a Vimeo Pro account and this works fine in other platforms. I get an error similar to this
"Access to video at 'https://vimeo-prod-skyfire-std-us.storage.googleapis.com/XXXXX' from origin 'XXX_WHATEVER_ORIGIN' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource"
To reproduce I just have to play any private video from my account in a webgl deploy
Unity 2018.3.7f1
Tested in Chrome using windows 10
The text was updated successfully, but these errors were encountered: