Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
6000.0.0b12
Issue ID
ISXB-803
Regression
No
[Android] Touch input is not recognized when button is pressed in the Player
Reproduction steps:
1. Open the attached project “TouchProject”
2. Build and Run on Android
3. Touch the button on the screen
Expected result: The button colour turns red
Actual result: The button colour remains white (i.e. The touch input isn’t recognised)
Reproducible with: 1.3.0, 1.5.1, 1.7.0, 1.8.1 (2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12)
Reproducible with these devices:
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9.0.0
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
OS: 9
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512,
Testing environment: macOS(Intel) 14.0 Sonoma, Windows 11 23H2, Windows 10 Pro 22H2
Notes:
1{-}. Changing the Input System from the New to the Old or Both doesn’t fix the issue{-}
- TomasD: Changing to Old Input fixes the issue:2. Not Reproducible on Standalone Player or The Editor
** Chance Input Handling to Input manager
* On EventSystem remove Input System component and Add Standalone Input Module instead
TomasD: Workaround:
** After launching the app
** Run scrcpy ([https://github.com/Genymobile/scrcpy/releases)] on PC
** Android screen will be shown on PC
** Tap with Mouse on Button it will get clicked
** Tap on Android device screen on the button, tapping starts to work.
** Probably something's incorrect with Input System UI module.
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
- Celestial bodies order remains unchanged when the Distance setting is modified
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
Resolution Note:
This is a setup mistake, following aspects are setup incorrect:
1. The control scheme "Touchscreen" has two devices "Touchscreen" and "Pointer".
- removing the Pointer device from the devices in the Touchscreen scheme solves this issue.
2. The "Touchscreen" scheme in the Binding configuration window is not ticked at touch bindings for The Actions UI/Click, UI/Submit and others.