[WASM] Strange startup errors in browser log

[DierkDroth]

The other day I updated my app to latest UNO bits and now have this error in the browser log.

Uncaught TypeError TypeError: Cannot read properties of null (reading 'querySelector')
    at initProgress (https://localhost:59847/package_b69930fda6c528d10ced43f3b632f9e89928ed1b/uno-bootstrap.js:232:33)
    at preInit (https://localhost:59847/package_b69930fda6c528d10ced43f3b632f9e89928ed1b/uno-bootstrap.js:173:14)
    at <anonymous> (https://localhost:59847/package_b69930fda6c528d10ced43f3b632f9e89928ed1b/uno-bootstrap.js:803:61)
Setting UNO_BOOTSTRAP_MONO_RUNTIME_MODE=Interpreter
Setting UNO_BOOTSTRAP_MONO_PROFILED_AOT=False
...
Done loading the BCL

Unfortunately I can't reproduce the issue in a fresh repo using same version(s) of UNO.

Any idea what might be going wrong?

[jeromelaban]

Thanks for the report. You will likely have previous errors associated with this, showing up in the logs. Which version of the bootstrapper are you using?

[DierkDroth]

@jeromelaban you mean from the browser console? Here you are (like I said the error is the very first entry in the log):
localhost-1661433041352.log

Please let me know if you needed something different

[jeromelaban]

Thanks. Do you override css files and/or index.html files?

[DierkDroth]

@jeromelaban please see attached

Files.zip

[jeromelaban]

It's likely that the changes made to the index.html file are causing issues here. Try without an index.html file.

[DierkDroth]

As I recall the index.html came from some UNO docs ... anyway:

• I removed it from the project
• cleaned the solution
• manually deleted obj/bin folders in the WASM project
• rebuild the whole solution

-> issue persists :-(

What else could I try?

[DierkDroth]

Alright after more tinkering I found the cause of trouble: this in fact was the index.html which is had in my project (which I added way back based on these docs - BTW the link to Templates/index.html is broken) - and - adding this to my project file

	<WasmShellIndexHtmlPath>index.html</WasmShellIndexHtmlPath>

Removing both fixed the issue -> good

@jeromelaban I recommend reviewing the docs and updating as needed to avoid further trouble in future.

[jeromelaban]

Thanks. The doc is being explicit when talking about this property, what would have made it clearer ?

[DierkDroth]

@jeromelaban a couple of issues:

• the link to the template/index.html is broken
• as the link was working - many months back - I pulled the template for index.html from that link and this caused the trouble I ran into