Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1127530
Regression
No
Input.GetKeyUp and Input.GetKeyDown always Return False when used in the Coroutine with WaitForEndOfFrame Return type
How to reproduce:
1. Open "SampleScene" Scene in the attached "UnityTest.zip" Project
2. Enter Play Mode
3. Press Spacebar on the Keyboard
4. Observe the numbers next to "OnUpdate" and "OnEndOfFrame" in the Game View
Expected Behavior: The Coroutine with WaitForEndOfFrame Return type recognizes the Input and the number next to "OnEndOfFrame" is Incremented
Actual Behavior: The Input Returns false in The Coroutine with WaitForEndOfFrame Return type and the number is not Incremented
Reproducible with: 2017.4.21f1, 2018.3.7f1, 2019.1.0b4, 2019.2.0a6
Note: The Input.GetKey works perfectly. You can see that the Coroutine that Returns "null" recognizes the Input and Increments the value next to the "OnUpdate" in the Game View. The issue is only present in the Editor, the Build behaves as expected. The code is in the "TextInputEndOfFrame.cs".
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 crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note:
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.