Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.1.2p3
Issue ID
981192
Regression
No
[UnityWebRequest] Wrong error code is returned if URL loading receives a system error
To reproduce:
1. Open project attached by the user
2. Make sure "Test" scene is opened
3. Enter play mode
4. Inspect the output in the console
Expected result: After system error happens, correct error code is returned
Actual result: Error code 0 is returned
Reproduced with: Unity 5.6.5p1, 2017.1.3f1
Newer versions (2017.2.1p2, 2017.3.0p2, 2018.1.0b4) throw IndexOutOfRangeException: Array index is out of range
Also reproduced on iOS platform with iPhone 7+ iOS 11.1
Fixed in: 2018.2.0a2
Comments (1)
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
GVanloo
Apr 04, 2018 19:42
Can this be backported to Unity 2018.1?