Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
1
Found in
2019.4
2019.4.14f1
2020.3
2021.1
2021.2
Issue ID
1326854
Regression
No
Dns.GetHostEntry malfunction in IL2CPP builds
Reproduction steps:
1. Open user attached Project
2. Open Assets\Scenes\SampleScene
3. Build and Run a Dev build using IL2CPP
Expected result: There are no errors in the console
Actual result: There's an error in the console
Reproducible with: 2019.4.24f1, 2020.3.5f1, 2021.1.4f1, 2021.2.0a14
Notes: Does not reproduce with the Mono backend
Comments (1)
-
NNSkelly
Apr 13, 2021 21:29
For readers, bug is specifically with passing string.Empty ('') to GetHostEntry. Microsoft official docs state that this should return the machine's current IP address(es), and indeed this is the most common forum/stackoverflow advice for detecting this information at runtime. In editor and in Mono builds, the invocation works as such, but in IL2CPP builds, it results in an error
SocketException: Could not resolve host ''
with a chain of 0000 addresses in the quoted stacktrace
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a16
Resolution Note (fix version 2021.1):
Fixed in 2021.1.10f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.12f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.29f1