Search Issue Tracker

In Progress

Fixed in 6000.0.36f1, 6000.1.0b1

Votes

4

Found in

6000.0.30f1

6000.1.0a7

7000.0.0a1

Issue ID

UUM-90583

Regression

No

[Android] [GameActivity] No input is being registered when "CursorLockMode.Locked" is used with "GameActivity" Application Entry Point

-

How to reproduce:
1. Open the “AndroidBugExample.zip“ project
2. Open the “Scene“
3. Build and Run for Android
4. Touch the device screen

Expected result: The “Sphere“ GameObject is de-activated
Actual result: Touch input is not registered

Reproducible with: 6000.0.30f1, 6000.1.0a7
Could not test with: 2021.3.46f1, 2022.3.54f1 (“GameActivity“ is not an option for Application Entry Point)

Reproducible environment: macOS 15.1.1 (Intel), Windows 10 (Reporters)
Not reproducible environment: No other environment tested

Reproducible with these devices:
VLNQA00511, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00518, Google Pixel 4 (Pixel 4), Android 13, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00107, Huawei Nexus 6P (Nexus 6P), Android 8.1.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77

Notes:
- Not reproducible when the cursor is not locked
- Not reproducible in the Editor and Standalone
- The only possibility to have the correct behavior for both Standalone and Android is to disable the Cursor lock with “#if !UNITY_ANDROID”
- After connecting a mouse to the device, the issue does not reproduce
- Not reproducible with Activity set as Application Entry Point

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.