Closed tomaszwozniak123 closed 1 year ago
This error isn't actually caused by the token; it's a side effect of the function that pre-loads available media devices. What browsers are your testers using? And are you running in a secure context (i.e. serving over https
or localhost
)? The logs seem to indicate that you're stumbling over the latter:
7565410@http://myapplication.cloudfront.net/Build/Build013.framework.js:1304:21
If you need test WebGL deployments, let me know if you'd be interested in using NatML. We offer free Unity WebGL hosting for our demos.
Our testers are using browsers: Mozilla Firefox v: 112.0.1 Chrome Safari
We use cloudfront environment for tests only currently with supported HTTP versions HTTP/2, HTTP/1.1, HTTP/1.0. Do you think that could be the reason?
My comment wasn't about HTTP versions; it was about being in a secure context. In simple terms, your URL should begin with https://
instead of http://
.
I think in this log we have http://myapplication.cloudfront.net/ instead of https, because the application didn't start yet fully (or sth like that - I am really guessing only). Our domain is https://myapplication.cloudfront.net/
Just so we're on the same page, can you share a screenshot of the URL bar in your browser when running your WebGL application?
Sure:
@tomaszwozniak123 what device and OS versions are your users on? navigator.mediaDevices
being undefined
isn't a NatDevice bug; it indicates that the browser that your app is running in is not providing access to media devices. The most common reason for this is when your app is running in an insecure context.
Hi, I have 3 testers on the team; one is testing our application daily. Two other testers were testing last time our application about a week ago. In the meantime, we updated nat VifeoKit to 0.0.13. Those two testers get error as shown below. Both of the testers cleared the browser cache and only for one it was a solution. We are using NatML VideoKit and Natml Meet Segmentation for WebGL Unity.