Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
933137
Regression
Yes
UriFormatException: Invalid URI when parsing file path with WWW class
Steps to reproduce:
1. Open attached "errorWWW.zip" Unity project
2. Open scene “Test”
3. Click on “GameObject” object in the Hierarchy tab
4. Manually enter “skyNight001.png” path on your computer into “File Path” field in the Inspector tab
5. Enter Play mode
Reproduced in: 2017.3.0a1, 2017.2.0b4, 2017.1.0p1, 2017.1.0f3, 2017.1.0f1, 2017.1.0b3, 2017.1.0b1
Didn’t reproduce in: 2017.1.0a6, 2017.1.0a5, 2017.1.0a1, 5.6.2p4, 5.6.1f1, 5.5.0f1
Regression introduced in: 2017.1.0b1
Error:
UriFormatException: Invalid URI: The hostname could not be parsed. ( )
System.Uri.Parse (UriKind kind, System.String uriString)
System.Uri.ParseUri (UriKind kind)
System.Uri..ctor (System.String uriString, Boolean dontEscape)
System.Uri..ctor (System.String uriString)
UnityEngineInternal.WebRequestUtils.MakeInitialUrl (System.String targetUrl, System.String localUrl) (at /Users/builduser/buildslave/unity/build/Runtime/WebRequest/Managed/WebRequestUtils.cs:481)
-------------------------
This bug is by design:
The newer Unity versions are more strict about URI conformance.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment