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
- Awaitable.NextFrameAsync() fails to resume when invoked multiple times from the playModeStateChanged event
- Text input duplicates in the TextField when textField.isDelayed is set to true and typing with a Japanese keyboard layout
- “AssetDatabase.GetMainAssetTypeAtPath" returns the incorrect type when using a global namespace class with the same name as a Unity type
- Editor silently crashes when switching platforms when Meta XR Core SDK is imported
- Crash on Object::SetCachedScriptingObject when entering the Play Mode immediately after stopping asynchronous operations in the previous Play Mode session
Add comment