Search Issue Tracker
By Design
Votes
11
Found in
2019.4
2019.4.18f1
2020.3
2021.1
2021.2
Issue ID
1322230
Regression
No
[iOS] Input.GetKey is delayed returning to False on key release on iOS build
Reproduction steps:
1. Open project in "M1InputTest.zip"
2. Build for iOS and open the project in Xcode
3. Connect a Keyboard to an iOS device
4. Deploy to an iOS device
5. Press and release a key on the keyboard while inspecting the debug UI in the application
Expected result: Input.anyKey will become true and stay so until you release the key
Actual result: Input.anyKey will become true and will stay true for a while after releasing the key
Reproducible with: 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Could not test with 2018.4.35f1 (project breaks)
Reproducible with:
iPhone 12 (iOS 14.1)
Not reproducible with:
OnePlus A5000, Android 10, Adreno 540, Snapdragon 835
Not reproducible with standalone or editor
Reproducible with M1 Catalyst build
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
- Unable to change the Shadow Map resolution for lights via Inspector when 'preserveCachedShadow' is enabled
- Adaptive Probe Volumes are not loaded when Adaptive Light Probes are exported via Asset Bundles and opened on another project
- Sprites are not present in Player when built
- TrackPropertyValue callback stops being called when modifying PropertyField
- [Android] [Particle System] "ParticleSystem.GeometryJob" sometimes takes up to ~20 ms in the worker thread when initializing 5 Particle Systems
Resolution Note (2022.1.X):
Unity does not support external mouse or keyboard input on iOS and iPadOS at the moment, this extends to iOS apps running on Apple Silicon Macs. To handle external mouse or keyboard input on Apple Silicon Macs please build your project as Standalone with "Architecture" set to "Intel 64-bit + Apple silicon".