We are having intermittent but fairly consistent CORS policy issues with the live-streaming-demo code. I am running your sample in Apache and using Google Chrome. I've tested both locally and on a hosted server with valid SSL.
Access to fetch at 'https://api.d-id.com/talks/streams/strm_wXeTNvuvh2TcZLuDE3fU6/ice' from origin 'http://127.0.0.1' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
These issues occur both during the connection process (pressing Connect) and when using POST to Create a talk stream (pressing Talk). Even when a connection is established Pressing Talk seems to regularly fail the first time and then work on subsequent presses.
I've been working on a prototype for a client. Trying to work around these intermittent CORS policy issues is really eating into our credits. Any suggestions would be appreciated.
We are having intermittent but fairly consistent CORS policy issues with the live-streaming-demo code. I am running your sample in Apache and using Google Chrome. I've tested both locally and on a hosted server with valid SSL.
Access to fetch at 'https://api.d-id.com/talks/streams/strm_wXeTNvuvh2TcZLuDE3fU6/ice' from origin 'http://127.0.0.1' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
These issues occur both during the connection process (pressing Connect) and when using POST to Create a talk stream (pressing Talk). Even when a connection is established Pressing Talk seems to regularly fail the first time and then work on subsequent presses.
I've been working on a prototype for a client. Trying to work around these intermittent CORS policy issues is really eating into our credits. Any suggestions would be appreciated.