Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2020.2.0a21
Issue ID
1269569
Regression
No
Invalid Windows Proxy Configuration causes NullReferenceException to be thrown incorrectly
User reported here: https://github.com/Unity-Technologies/mono/pull/1330
Repro Steps:
Have your windows registry values set as such:
HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ProxyEnable was set to true (1)
but HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings\\ProxyServer was set to null -- or not set at all
Run SampleScene in the attached project. Observe NullReferenceException that's thrown. Originates from: InitializeRegistryGlobalProxy
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
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- "UnityEngine.SystemInfo.processorFrequency" logs a value of 0 on M1 macs
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
Resolution Note (fix version 2020.2):
Fixed issue where an invalid windows proxy configuration would cause mono to ungracefully throw a NullReferenceException in AutoWebProxyScriptEngine.cs
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.29f1