We have encountered many a such issue that when running DWT in WASM mode, it doesn’t get past the step that says ‘Activating the WebTwain instance’.
The cause is that the wasm has been served with an incorrect MIME type in which case the browser won’t be processing the wasm after it is downloaded as it doesn’t know how to handle such files, therefore it stops dead there. To confirm the issue, open dev tools and switch to network and you’ll see something similar to this (note that content-type is wrong, it may not be what you see in this example but it’s definitely not application/wasm.
Notice that there are no more activity after this in network.
If it’s right, more wasm files will follow like this:
Make sure the wasm files can be served correctly. Different servers are configured differently. Here are some popular ones:
In this article: