Unity account

You need a Unity Account to shop in the Online and Asset Stores, participate in the Unity Community and manage your license portfolio. Create account

Language

Question by mattbrandmm · Oct 11, 2018 at 12:19 AM · webgl

Why does UnityLoader Code URL corruption not return an error with WASM?

I am having some trouble tracking an error that used to be caught using ASM. Basically there are 2 files that UnityLoader loads that we check for errors on - the framework url and the code url.

The code url in 2018 with wasm no longer returns an error from UnityLoader.js when it is corrupted.

This worked in 2018, with asm. So if the asm code url was corrupted, we would get the following js errors to our logs: Uncaught TypeError: Module.asm is not a function Uncaught SyntaxError: Unexpected token <

But with wasm, if the wasm code url is corrupted, we don't get any errors in our logs. This is an issue because we will not see the issue if player loads fail in this manner, it is silent log-wise.

Any ideas why the error is not being triggered anymore?

Add comment

Welcome to Unity Answers

The best place to ask and answer questions about development with Unity.

To help users navigate the site we have posted a site navigation guide.

If you are a new user to Unity Answers, check out our FAQ for more information.

Make sure to check out our Knowledge Base for commonly asked Unity questions.

If you are a moderator, see our Moderator Guidelines page.

We are making improvements to UA, see the list of changes.