Search Issue Tracker
Active
Under Consideration for 6000.0.X
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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment