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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.