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
- The Editor becomes unresponsive and memory allocation errors are spammed in the Console when Generating Lightning
- Crash on BatchApplyPropertiesFromSourceAssetDB when opening a specific project
- Scene view Camera cannot be moved with WASD/QE keys when the Right Mouse Button is held down and the Mouse is not moved
- Crash when calling default interface method from virtual method with same name
- [Android] Unity does not include the ".aab" extension for an AppBundle when it is built via script with the buildPlayerOptions.locationPathName = "AppName.apk" and EditorUserBuildSettings.buildAppBundle = true
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.