Search Issue Tracker
Duplicate
Votes
14
Found in [Package]
1.1.0-preview.1
Issue ID
1273300
Regression
No
[Input System][macOS] Keyboard button A is triggered when taking a screenshot with built-in tools
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. Focus the Game View Window
4. Take a screenshot (shift+cmd+4 shortcut to enable the tool and drag a box to take it)
5. Observe the Console Window
Expected result: Keyboard button A is not triggered when taking a screenshot with built-in macOS tools
Actual result: Keyboard button A is triggered when taking a screenshot with built-in macOS tools
Reproducible with: 2019.4.9f1, 2020.1.4f1, 2020.2.0b1 (0.2.10-preview, 1.1.0-preview.1) Couldn't test with: 2018.4.26f1 (0.2.1-preview) Couldn't test with packages lower than 0.2.10-preview (couldn't resolve errors) Note: "A" is also triggered when switching to the Editor with CMD+Tab shortcut from another application (GameView should be focused beforehand)
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
- [Vulkan] Release memory after deleting image
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Crash on internalABP::BoxManager::prepareData when entering Play Mode
- Crash at "UnityEngine.Object:FindObjectsOfType" when quitting the Player
Toastie_Rob
Jun 15, 2021 13:45
Is this the related bug report? If so, fixing in 2019.4 LTS instead of 2021.1.0a1 would be greatly appreciated.
https://issuetracker.unity3d.com/issues/macos-input-debugger-shows-invalid-key-state-after-a-shortcut-which-temporarily-freezes-the-screen?_ga=2.38425568.2137508895.1623758802-1379735735.1598890932&_gl=1*1ridnu2*_ga*MTM3OTczNTczNS4xNTk4ODkwOTMy*_ga_1S78EFL1W5*MTYyMzc2MzUwOS4yMi4xLjE2MjM3NjQxMzEuNDI.
allergicracoon
Jan 11, 2021 10:23
I would also like to see a fix for this issue
_Adriaan
Jan 07, 2021 09:28
Frustratingly, the duplicate issue is nowhere to be found on Unity Issues! Is the fix for this planned for 2019.4?
FredTuna
Oct 14, 2020 21:38
This happens in 1.0.0 (2019.4 verified) as well. We are using the new input system 1.0.0 in our project since it came out of Preview. Unfortunately, this bug prevents us from using the Input System in a released project and should be fixed for 2019.4 LTS since there doesn't seem to be any work around.