UI version ‘11.6.1’
Core version ‘11.6.1’
webviewer.min.js ‘11.6.1’
Build ‘7/16/2025 0f5e67641’
WebViewer Server false
Full API false
UI ‘default’
Do you have an issue with a specific file(s)?
Can you reproduce using one of our samples or online demos?
Are you using the WebViewer server?
Does the issue only happen on certain browsers? I am using chrome
Is your issue related to a front-end framework? Angular
Is your issue related to annotations?
Please give a brief summary of your issue:
I am seeing this warning on the console
webviewer-core.min.js:225 Your server has not been configured to serve WebAssembly threads. See https://docs.apryse.com/documentation/web/faq/wasm-threads for instructions on how to resolve this.
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
It seems like you’re encountering issues with enabling WebAssembly Threads in your WebViewer setup. This often involves configuring your server to be “cross-origin isolated,” which is necessary for enabling SharedArrayBuffer, a requirement for WebAssembly Threads.
Some things you can try:
Ensure that your server is set up with the appropriate HTTP headers to enable cross-origin isolation. Specifically, you need to set the Cross-Origin-Opener-Policy to same-origin and the Cross-Origin-Embedder-Policy to require-corp.
Verify that these headers are being applied correctly to the page where WebViewer is embedded, as well as the path serving the WebViewer’s lib folder.
Check the browser console for any additional errors or warnings that might indicate what’s going wrong with your current setup.
Make sure that your changes are applied and effective, as sometimes server configurations might not take effect immediately due to caching or other factors.
Here are some resources that might help you:
Cross-Origin Isolation Guide: This guide provides details on how to configure your server for cross-origin isolation.
