Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
6
Found in
2017.3.0b1
2017.3.0f2
Issue ID
981757
Regression
Yes
[WSA] isNetworkError always return true when running an UWP app on x86 architecture
Steps to reproduce:
1. Open the attached project (webrequestCheck.zip)
2. Open the "a" scene
3. Switch platform to Windows Store
4. Build for Universal Windows Platform
5. Open the generated Visual Studio solution and build a Debug x86 build
6. Observe the "isError DefaultTrue" message in Output
Expected result: isNetworkError should return false
Actual result: isNetworkError returns true
Note:
Unable to test with 2017.3.0a1 - 2017.3.0a7 due the errors
Reproduced with: 2017.3.0b1, 2017.3.0p2, 2018.1.0b2, 2018.2.0a1
Not reproduced with: 5.6.4p4, 2017.1.3f1, 2017.2.1p2
Fixed in: 2018.2.0a4
Backported: 2017.4.2f1, 2018.1.0b11
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
- Shader warnings are thrown after building High Definition 3D template
- "EndLayoutGroup: BeginLayoutGroup must be called first" error is thrown when changing Shader Precision Model from the Build Profiles window
- White artifacts/outlines are visible in the Garden Scene when viewing at meshes from a distance
- Shader warnings "Sprite-Unlit-Default" are thrown after building 2D Platrformer Microgame Template
- [Android] HLSL shader becomes corrupted when running on an Android device
jghospital
Feb 16, 2018 09:19
Future Release, but when is it going to be released?
Same bug here, works in editor but not in UWP Hololens device.
StephenHodgson-Valorem
Feb 06, 2018 16:54
What version was this fixed in?
TobiasWa
Jan 23, 2018 07:30
Reproduced on 2017.2.0f3, is there a known workaround?
markgrossnickle
Jan 18, 2018 22:03
Reproduced on 2017.3.0f3 targeting UWP x86
awonnink
Jan 17, 2018 14:24
UnityWebRequest seems to give unpredictable results when used on UWP, also for x64. Results might be dependent on the computer used.