Search Issue Tracker
Feature Request
Votes
0
Found in
2020.3.46f1
2021.3.21f1
2022.2.10f1
2023.1.0b6
2023.2.0a6
Issue ID
UUM-29491
Regression
No
[Android] Keycode events aren't or randomly detected when triggering via adb tool
How to reproduce:
1. Open the attached “IN-34670” project
2. Build and Run the “SampleScene” Scene on Android
3. Connect the device via adb
4. Execute multiple times “adb shell input keyevent KEYCODE_BACK” command in the Terminal
Expected result: Three events are detected and correspondingly printed in the Player: the new input system press and release, and the old system press event
Actual result: Only the old system event detected or new input system events are triggered randomly
Reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.10f1, 2023.1.0b6, 2023.2.0a6
Reproducible with devices:
VLNQA00513 - OnePlus Nord N10 5G (BE2029), CPU: Snapdragon 690 SM6350, GPU: Adreno 619, OS: 11
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
(user’s info) Magic Leap 2
Reproduced on: macOS 13.0 (Intel)
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
- Inconsistent Placement of Search Clear (X) Icon in "Preset Manager"
- Gradient Editor window bottom-right gradient marker color is incorrect
- MaskField tooltips should only display Value when bound
- Reordering Enum Values in VFX Graph Uint Property expands the “Value” field
- Visual Effect Graph sample titles display in non-human-readable format
Resolution Note:
adb input not currently supported while using the new input system.
Submitted as a Feature Request for future work.