Note: You will need one origin trial per domain name used to access your application. That’s why in my example there are twice per origin trial since we have two different domains to access our application.
But i guess your application was working before switching on the 1.9.9, is that correct ? Which version were you using before that ? I’m curious cause these two origin trial are almost mandatory since several weeks / months now, and should be used since version 1.9.0 if my memory is correct (for SIMD)
Another thing: what version of Chrome are you using for your tests ?
Apologies for not replying sooner. nvivot, who is my colleague, already shared how we did it.
SharedArrayBuffer stopped working (video would stop working) from Chrome 92 if web isolation is not implemented on your application yet. So, as a temporary workaround, we used the SharedArrayBuffers Origin Trial on our application. As nvivot pointed out, you need to use the meta tag for the origin trial token. The token is per domain. So, if you have different environments (local, dev, staging, production), then you need to get tokens per each environment domain.
So, you officially do not support the credential less ? I though you mentioned it but in the end it’s not in the linked documentation.
Anyway, for anybody who want to understand web isolation & the different modes available, just go on chrome documentation. You won’t get a better and less confusing documentation than from the people who made it.
In your application, are you using 3rd party libraries that communicate with 3rd party services, or you own in-house services, that are not compliant with web isolation (they do not returns the expected headers in their HTTP response) ?
You should have some warning or error indicating that at least one part of your application cannot be isolated and therefore the web isolation is deactivated.
In such situation, even if you have the web isolation on your application, it will be dropped because of such 3rd party calls from your application, and because of the web isolation being deactivated, the SharedArrayBuffer will also be deactivated, making the Zoom Web SDK not working.
Now… if you have the SharedArrayBuffer Origin Trials, then you do not need to implement web isolation. Our application is working without.
What we did not test (and it seems to be your situation) is the usage of both the web isolation with potentially a 3rd party service not compliant (that would then affect the shared array buffer feature, with the shared array buffer origin trial. I’m not sure what would be the priority for Chrome between:
the deactivation because web isolation is deactivated
the activation because you use the origin trial
So, in your position, i would first remove the web isolation (since you use the origin trial), and test your application to:
check whether it works without the web isolation
check if you have a warning in the console log saying that the shared array buffer feature will require web isolation from chrome 93 (something like that, i don’t remember exactly the log message)
If you application works (audio & video), then you have your answer. If not, the problem is somewhere else and not related to web isolation.
If you have shared array buffer when you activate web isolation, but not when you do not activate web isolation and use the shared array buffer OT, this confirm that your origin trial for shared array buffer is invalid.
An origin trial works for a specific domain / host name, and for a certain period. You should verify your current OT whether it applies to the correct host and is still valid (not ended). In all case, it’s probably easier to just re-create a token for this origin trial (with the expected host name), replace & test again with only the shared array buffer origin trial without web isolation. I don’t see any (obvious) reason for that not to work.
I suspect that your generated your shared array buffer origin trial before they extends the date to July 2022 (due to recent decision) and therefore, unless you renewed in between, the original date was until the end of Chrome 92.
Please renew it, and the validity / working period would be up to July 2022 for your new token.