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
- "Object reference not set to an instance of an object" is thrown when destroying a GameObject with a Camera Component
- [Android] The error message "OPENGL NATIVE PLUG-IN ERROR: GL_OUT_OF_MEMORY:" is thrown when the video is playing
- [IL2CPP] Build fails with the error "[1mcannot convert 'Nullable_1_tEA06D91799914C5C8830F83CE2A8395868C14F02' to 'int32_t' (aka 'int') without a conversion operator" when IL2CPP is used as the Scripting Backend
- Rigidbody interpolation is performed after the next frame's FixedUpdate() when using Rigidbody2D
- OnAudioFilterRead not working as expected for generator scripts
Add comment