Hi @armanayra, Welcome to the forums.
WebGL building is not something that we support. There have been previous attempts to get this working, but unsuccessful due to a few reasons.
-
Unity WebGL doesn’t support the
System.Threadingnamespace, which we use throughout core, and the Unity Connector.- There are some reports of people getting
System.Threadingworking, but nothing official.
- There are some reports of people getting
-
Our Sharp Core has managed dependencies (sqlite)
- I’m unsure how Unity handles managed DLLs for WebGL building, It may not be possible.
-
Not a hard blocker, but WebGL has no disk access, so we can’t load accounts, or cache objects the same way as normal. But there are workarounds, see this thread.
Taking a look at our main branch, building for WebGL fails with some dependency conflicts.
This is because several of the managed dlls are being included for WebGL builds, which causes some conflicts.
I was able to get a build working, by simply disabling all but the win-x64 managed assemblies. (see this branch) However, trying to run this yielded the common “stuck at 90% progress” problem.
This maybe because of System.Threading, or SQLite…
You are welcome to experiment more,
However, I fear you may run-into the same blockers I did. WebGL building may simply not be possible without some serious restructuring of our core.
Perhaps you have some deeper insights to workaround Unity WebGL’s limitations. It’s not something I’m intimately familiar with developing for.
I’d be happy to discuss this further, and see what progress we can make. But I can make no promises from our end.