Search Issue Tracker
Fixed in 2018.1
Fixed in 5.6, 2017.1, 2017.2, 2017.3
Votes
1
Found in
2017.1.2p1
Issue ID
960914
Regression
Yes
[iOS][A11] Screen.dpi() method return incorrect number of DPI on iPhone 8, 8+
To reproduce:
1. Open attached project
2. Open build settings, select iOS platform and add "main" scene
3. Build and run project on a device with A11 SoC
4. Check console in Xcode
Expected result: Screen.dpi() should return correct value of DPI
Actual result: Screen.dpi() returns 0
Reproduced with: 2017.1.2p1, 2017.3.0b5, 2018.1.0a1
Not reproducible with: 2017.1.2f1
Regression since 2017.1.2p1
Device: iPhone 8 iOS 11.0.1
Not reproducible on iPhone 6s iOS 11.0
Fixed in 2018.1.0a2
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
- When "draw instanced" is changed for entire terrain group and then undone, it is only undone for the terrain that was selected
- Custom Inspectors OnDisable still called after Asset has been deleted
- Native Plugin regression from 2018.x results in "DllNotFoundException" error
- [Android] "AndroidETC2FallbackOverride.Quality32BitDownscaled" does not work on an Atlas created with the Legacy Sprite Packer
- Debug.Log() Context not highlighted when pressed after printing in Test Runner's EditMode
Ethan_VisualVocal
Oct 20, 2017 22:20
Er, rather, our touch-vs-drag threshold calcs based on DPI are way off. Using sane default DPI values to work around for now.
Ethan_VisualVocal
Oct 20, 2017 21:11
Yeah, this is causing us some crazy issues with touch events. =(