Search Issue Tracker
By Design
Votes
2
Found in
2022.3.14f1
2023.2.2f1
2023.3.0a16
6000.0.0b11
7000.0.0a1
Issue ID
UUM-57932
Regression
Yes
[Android] PointerEventData.pointerId value is incorrect when pressing a finger on the screen
Steps to reproduce:
1. Open the attached “TouchTest” project
2. Build And Run the project on the device
3. Observe the device’s screen while pressing a finger on the screen multiple times
Expected result: Shows text with each finger identification number
Actual result: Shows “5” text
Reproducible with: 2022.2.0a10, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16
Not reproducible with: 2021.3.33f1, 2022.1.24f1
Could not test with: 2022.2.0a1-2022.2.0a9 (gradle errors)
Testing environment: macOS Sonoma 14 (Intel)
Not reproducible on: No other environment tested
Reproducible with devices:
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13
Google Pixel 7 Pro (by user)
Not reproducible with devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00513 - OnePlus Nord N10 5G (BE2029), CPU: Snapdragon 690 SM6350, GPU: Adreno 619, OS: 11
VLNQA00017 - Huawei Nexus 6P (angler), CPU: Snapdragon 810 MSM8994, GPU: Adreno 430, OS: 8.0.0
Notes:
- Shows IDs except for 1st finger when pressing multiple fingers at the same time with lower than 1.6.3 Input System package version
- Reproducible regardless of UGUI or Input System package versions
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
Closing this. To make this work, the Pointer action needs to be setup to Passthrough type to bypass "conflict resolution".
When on Windows w/ Touchscreen and using a InputAction of "Value" type, we receive both Mouse and Touch position event and decide which one to use based on the highest magnitude. Passthrough type doesn't not care about this and provides correct values for this particular case.