Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X
Votes
2
Found in
5.6.1f1
Issue ID
914981
Regression
Yes
[WSA] WWW requests do not appear in Fiddler with UWP build
Steps to reproduce:
1. Open the attached project (UWPFiddlerRepro.zip)
2. Switch platform to Windows Store
3. Build for WSA Universal 10 (.NET backend), Build type - XAML, Enable C# projects, Enable Development build, Enable Copy references
4. Open Visual Studio solution
5. Deploy on local machine (DEBUG)
6. Set up Fiddler to trace requests on your PC
7. Use the WinConfig option in Fiddler to enable loopback exemptions so you can see UWP web traffic (you may need to restart Fiddler)
8. Press any key to send a request to 'www.google.com'
9. Observe that the request to www.google.com initiated from the Unity WWW request does not appear in Fiddler
Expected result: WWW request should appear in Fiddler
Actual result: WWW request does not appear in Fiddler
Reproduced with: 5.5.4f1, 5.6.1p2, 2017.1.0b8
Not reproduced with: 5.5.1f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment