Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.2
2021.2.7f1
2022.1
2022.2
Issue ID
1398587
Regression
No
Project fails to build for WebGL when using NumSharp
How to reproduce:
1. Open the user's attached project
2. Build the project for WebGL (File -> Build Settings -> Build)
Expected result: the build is completed successfully
Actual result: the project is unable to build
Reproducible with: 2021.2.16f1, 2022.1.0b13, 2022.2.0a8
Could not test with: 2019.4.37f1, 2020.3.32f1 (third-party assembly 'NumSharp' error)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2022.2.X):
Thank you for logging the bug here. One of our developers is working with Emscripten to get this fixed. You can track here: https://github.com/WebAssembly/binaryen/pull/4567. We plan to integrate this into a future version of the Unity Editor.