Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.28f1
2022.3.5f1
Issue ID
UUM-44060
Regression
No
[Android] Gamepad trigger is stuck in performed phase when pressed and released in Player
How to reproduce:
1. Open the “IN_47346” project
2. Press Windows → Analysis > Android Logcat
3. In the Android Logcat search bar type “Shoot values”
4. In the Build Settings “Run Device” dropdown select the connected device
5. Press Build And Run
6. Connect the PS4 or PS5 controller to the Android device
7. On the controller press the Right Trigger, hold it for a second and release it
8. Repeat step 7 multiple times
Expected result: “Shoot values” doesn’t get stuck
Actual result: “Shoot values” does get stuck and spam the same value repeatedly
Reproducible with: 2021.3.28f1, 2022.3.5f1
Not reproducible with: 2023.1.5f1, 2023.2.0b1
Testing environment: Windows 10 Pro
Reproducible on these devices:
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00530, Sony Xperia 5 III (XQ-BQ52), Android 11, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Not reproducible on these devices:
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00520, Samsung Galaxy S22 (SM-S901U), Android 12, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 9, CPU: NOT FOUND, GPU: Adreno (TM) 630
Couldn’t test on these devices due to the controller not connecting:
VLNQA00512, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Notes:
- Not reproducible with WebGL, WindowsStandalone, iOS
- Not reproducible with Xbox One controller
- Reproducible on PS4 and PS5 controllers
- User also mentions that when the issue is reproducible the “holdDownTime” value increases without stoping
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Based on our priorities we don't think we'll be able to look into this in the foreseeable future.