Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.15f1
Issue ID
UUM-59151
Regression
No
[Android] Touch input is not recognized when pressing a button in the Player
Reproduction steps:
1. Open the attached user’s “ASDQWE” project
2. Build and run the Player (File > Build And Run)
3. In the Player, wait for the Scene to load and press the “Touch Me, Please” button
Expect result: The text field “Welcome to…” disappears
Actual result: The text field “Welcome to…” does not disappear
Reproducible with: 2022.3.15f1
Could not test with: 2021.3.33f1 (“Execution failed for task ':launcher:processReleaseResources'“ build error), 2023.2.4f1, 2023.3.0a18 (Could not resolve compilation errors from the user’s scripts)
Reproducible environment: macOS 14.1.2 Sonoma (intel), Windows 10 (user’s)
Not reproducible environment: No other environment tested
Reproducible with these devices:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00146, Htc 10 (HTC 10), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Not reproducible with these devices:
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
Could not test with these devices:
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660 (The Player does not get past the initial Scene)
Notes:
- The user stated that this issue was fixed by switching The Input System from the New to the Old or Both in a different project
- The user stated that this issue does not reproduce on iOS devices
- Could not test macOS Standalone Player (“ETC1 compressed textures are not supported when publishing to Standalone” build error)
- Could not test with iOS devices (“'IronSource/ISSupersonicAdsConfiguration.h' file not found" error)
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.