Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.2.1f1
Issue ID
1007047
Regression
No
[Android] External keyboard does not set Input.GetKey(KeyCode.Return) to true when return key is pressed
Reproduction steps:
1) Download attached project - 1007047_externalkeyboard.zip
2) Build and run it on an Android device
3) Connect external keyboard to the device
4) Try hitting enter (return) key
-- Notice that UI text element stays "New Text"
Expected result:
Input.GetKey(KeyCode.Return) and Input.GetKeyDown(KeyCode.Return) from the "NewBehaviourScript.cs" should change this text, indicating that the key was pressed
Note:
Instead of Input.GetKey(KeyCode.Return), return key on a keyboard is mapped to (KeyCode)10
Reproduced with:
2018.2.0a1, 2018.1.0b9, 2017.3.1p2, 2017.2.2f1, 2017.1.3p2, 5.6.5p2, 5.5.6f1
Devices under testing:
Reproduced with:
Google Pixel 2, Android 8.1
Samsung Galaxy Note 8, Android 7.1
LG G3, Android 5.0
Comments (1)
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
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- [Linux] Numeric field value stops increasing when cursor reaches the edge of the monitor while dragging
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- "Add Component" button overlaps the Volume component UI when creating a new Volume Profile in a wide Inspector on high-DPI scaling
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
mossflower
Apr 01, 2018 02:36
This is a somewhat annoying issue. Is there any workaround?