-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unable to create web-worker if SharedArrayBuffer is enabled #1103
Comments
Literally came here to log the same issue. We have a client hoping to make use of this. It looks like assets come from a different server and that one doesn;t set the COOP + COEP headers that are required for secure features e.g. sharedarraybuffer and workers |
Do we know what the solution to this is? |
@mvaligursky It should be the same that you did to add SharedArrayBuffer support. All of the servers you use need to return COOP and COEP http headers. |
We use credentialless for Cross-Origin-Embedder-Policy if SharedArrayBuffer is enabled require-corp credentialless |
right, so the headers are set for the launch page only and should be set for the worker as well |
could you build me a test case please? |
i prepared a fix, will be deployed soon |
Eagerly waiting ;) |
@LeXXik It should be Monday morning. 😄 |
the fix is deployed, please test your projects |
@MAG-AdrianMeredith Those errors are because the scripts are not loaded as modules, so static imports and import.meta are invalid. This will be fixes soon, but for now you can see if there is a UMD/CJS build of the library you're using |
It works on my end. Thank you! Although, it throws an issue with Draco. I will open another ticket for it. |
Unable to create a web-worker, if SharedArrayBuffer option is enabled.
Repro: https://playcanvas.com/project/1191623/overview/corp-issue
The text was updated successfully, but these errors were encountered: