Hello, I’m trying to use the UI Toolkit, just some very basic stuff, 1 UIDocument with 1 Scroll Panel, with several buttons inside it, no custom external style, all the styles for elements are inlined… I haven’t even bound any events yet, just displaying the layout.
Everything works perfectly as it should in editor, but when I run the WebGL version, the UI doesn’t display (the rest of the things in game still works properly), and I get the following series of exceptions:
comics.framework.js:2 A scripted object (probably UnityEngine.UIElements.ThemeStyleSheet?) has a different serialization layout when loading. (Read 56 bytes but expected 128 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script (UnityEngine.UIElements.PanelSettings) on this Behaviour is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script on this Behaviour (Game Object ‘’) is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 A scripted object (probably UnityEngine.UIElements.PanelSettings?) has a different serialization layout when loading. (Read 48 bytes but expected 200 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script (UnityEngine.UIElements.ThemeStyleSheet) on this Behaviour is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script on this Behaviour (Game Object ‘’) is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 A scripted object (probably UnityEngine.UIElements.ThemeStyleSheet?) has a different serialization layout when loading. (Read 40 bytes but expected 67808 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script (UnityEngine.UIElements.VisualTreeAsset) on this Behaviour is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script on this Behaviour (Game Object ‘’) is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 A scripted object (probably UnityEngine.UIElements.VisualTreeAsset?) has a different serialization layout when loading. (Read 40 bytes but expected 3304 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script (UnityEngine.UIElements.UIDocument) on this Behaviour is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 The referenced script on this Behaviour (Game Object ‘UIDocument’) is missing!
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 A scripted object (probably UnityEngine.UIElements.UIDocument?) has a different serialization layout when loading. (Read 32 bytes but expected 72 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
_JS_Log_Dump @ comics.framework.js:2
comics.framework.js:2 UnloadTime: 5.699999 ms
I hope someone will have some suggestions?
Oh, btw, I have WebGL Compression disabled, since that was causing a freeze on load (at least in the previous version of unity).
Depending on your version, there used to be an issue with the IL2CPP code stripping that could cause this exact behavior. This only usually happened on a new project that only used a scene with a plain UIDocument, UXML and no custom code.
The workaround is to create a custom component that refers to UIDocument and to add it in your scene.
Hi, sorry to necropost, but this is the only clue I have on the very same problem. I tried applying the workaround by attaching the custom script to my UIDocuments, but the serialization errors remain and UIs are still invisible in WebGL builds. Is there something else I could try?
Has anyone been able to verify that this is actually fixed? It is not fixed for me in Unity 2022.2.0a10 (on Linux). Also, the workaround above does not work for me. At runtime I get errors about different serialization layouts and referenced scripts being missing. CodeStripperWorkaround.cs prints “Hello!” and nothing else, so I guess the UIDocument doesn’t make it into the build.
Does anyone know how to get UIToolkit to work in a WebGL build?
I think the bug has not been fixed in 2022.2.0a10.
I open my project by 2022.2.0a10 and rebuild to platform WebGL. Nothing changed, just like 2022.1.0.b11.
No matter whether I use “CodeStripperWorkaround.cs” or not.
