Search Issue Tracker
Fixed in 2018.1.X
Votes
3
Found in
2017.1.2p1
Issue ID
967012
Regression
No
[iPhone X] Safe area is being ignored when typing text to input field
When opening a keyboard to type text (input field set to multiline) it ignores safe area and some characters are typed "behind the screen".
How it looks like: https://imgur.com/a/0UDt5
To reproduce:
1. Open project attached by the user.
2. Build "TestKeyboardIphone" scene for iOS
3. Run it on iPhone X
Expected result: Text should be typed only in the safe area
Actual result: Safe area is ignored
Won't Fix:
This is correct and intended behavior. The user has to code his application considering iPhone's X safe area on the UI level. There is an API that should take care of this. Scree.safeArea (may be currently unavailable since it's newly implemented API). Alternatively, you can check this solution: https://bitbucket.org/p12tic/iossafeareasplugin
Comments (1)
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Zachary625
Mar 16, 2018 13:38
I'm not quite sure about my correctness of understanding in the "Won't Fix" part of the bug report(That is not Unity3D official response, right?), the way I see it is that there might be no solution by Unity3D users on C# level. Even if we took care of the safe area for canvas, the keyboard and the contained native input zone would still be managed by iOS itself and customized by Unity3D native code. We're using 5.6.3f1 with XCode 9, on iPhone X it looks exactly the same as the image posted by the reporter.
Also, I'm not sure this is even fixable by Unity3D, probably only fixable by iOS patch...yet I would love to hear more about this issue :D