Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
1
Found in
2019.4
2020.3
2021.1
2021.2.0a19
2021.2.0b5
2022.1
Issue ID
1355543
Regression
Yes
[iOS] Input from an external keyboard is not handled when running a Build
Reproduction steps:
1. Open attached project "KeyboardTest" and load Scene "SampleScene"
2. Build and Run the project on an iOS device
3. Connect an external keyboard to the device
4. Press the Space key on the connected Keyboard
5. Observe the Xcode Console
Expected result: "Space is GetKeyDown" and "Space is GetKey" is logged to the Console
Actual result: Nothing gets logged to the Console
Reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0a19, 2021.2.0b7, 2022.1.0a5
Not reproducible with: 2021.2.0a17
Could not test with: 2021.2.0a18 (Version fails to install)
Reproduced with:
iPhone 6 (iOS 12.4.8)
iPhone 7 (iOS 12.3.1)
iPhone 12 Mini (iOS 14.1)
Note:
- Input Fields are still able to process Input from an external keyboard
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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a7
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b12
Resolution Note (fix version 2021.1):
Fixed in 2021.1.21f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.19f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.31f1