Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
0
Found in
2018.4.9f1
2019.2.7f1
2019.2.9f1
2019.3.0b4
2020.1.0a4
Issue ID
1191670
Regression
Yes
[iOS] Network.NetworkInterfaceType always return 0
Steps to reproduce:
1. Open attached project "NetworkTest"
2. Make sure that SampleScene is included in Build Settings
3. Build for iOS and deploy the Xcode project to the iOS device
4. Observe Xcode console
Expected result: network.NetworkInterfaceType reads "Loopback", "Ethernet", etc
Actual result: network.NetworkInterfaceType returns 0
Reproduced in: 2018.4.9f1, 2018.4.12f1, 2019.2.7f1, 2019.2.12f1, 2019.3.0b4, 2019.3.0b10, 2020.1.0a4, 2020.1.0a12
Not reproduced in: 2018.4.8f1, 2019.2.6f1, 2019.3.0b3, 2020.1.0a3
Note:
1. OperationalStatus is alwaysUnknown
2. network.GetIPProperties().UnicastAddresses is always empty
Devices reproduced on:
iPhone 8 Plus (iOS 12.0)
iPhone X (iOS 13.0)
Devices not reproduces in:
VLNQA00257, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
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
- Visual C# Compiler fails to locate assembly if response file compiler argument path contains spaces
- Constantly creating and destroying CharacterController component causes a memory leak
- Memory usage 20GB when importing Common USS stylesheets
- Custom built DLL's scripts which have classes derived from UIBehaviour cannot be added as a component after deleting Library
- WebGL WaitForSeconds works incorrectly on low fps
Resolution Note (fix version 2018.4):
Fixed in 2018.4.16f1