Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b14
Issue ID
650644
Regression
No
HTTP error codes returned by a server in a WebGL project cause JavaScript exceptions
HTTP error codes returned to a HTTP requests done using WWW class if published to WebGL fail with JavaScript exception.
Some client-server interaction relies on codes like 401 (not authorized).
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