Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.21f1
2021.1
2021.2
2022.1
Issue ID
1381212
Regression
No
[iOS] Touch input returns position relative to UIView instead of screen space when tapping inside native UIView
Reproduction steps:
1. Download and open the attached "TouchIncorrectPositionExample.zip (65.7 KB)" project
2. Build and deploy the project to iOS
3. In the device, press below the white square
4. Observe the "x" and "y" coordinates
5. Press the bottom corner of the white square
6. Observe the "x" and "y" coordinates
Expected result: The coordinates are relative to the space screen
Actual result: The coordinates are relative to the white square
Reproducible with: 2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.4f1, 2022.1.0a15
Reproduced with: iPhone 12 Pro (iOS 14.2.1), iPhone 6S (iOS 13.3.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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note (2022.1.X):
This is by design, as we pass the touch coords into Unity direct from the UIResponder delegate methods, however you can use UnitySetViewTouchProcessing() in the trampoline to tell Unity to convert these coordinates internally.