Search Issue Tracker
By Design
Votes
0
Found in
5.3.1f1
Issue ID
759297
Regression
No
Building for WebGL fails when CrashReporting.Init(String) is present in a script
To reproduce:
1. Open the attached project.
2. Build to WebGL
In the console, there should be three errors indicating that UnusedBytecodeStripper2.exe did not run properly and the build wasn't built.
Expected result: the build succeeds, there are no errors.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment