Search Issue Tracker
Fixed in 5.2.2
Votes
46
Found in
5.2.0f3
Issue ID
726017
Regression
Yes
[OSX] Input.inputString, GetKey etc. does not work on Mac OSX
Steps to reproduce:
1. Open the attached project
2. Open 'InputStringTest' scene
3. Play the scene
4. Click any of the keyboard buttons
5. Watch the console, notice no input is logged despite the Debug.Log(Input.inputString) being called each frame.
Note: Works as expected on Windows.
Other users report also Input.GetKey, Input.GetKeyDown,
Input.GetKeyUp and Input.GetButton as broken
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
shochet
Oct 09, 2015 19:57
Can anybody confirm the most recent version of Unity before this problem? I tried 5.1.4 but it has the same bug. When was the bug introduced?
EdwinLyons
Sep 29, 2015 11:53
According to an email I just got from support, they expect to fix this in a 5.2.1 patch release, hopefully the next one (which I guess comes out on Friday).
zbyhoo
Sep 27, 2015 19:44
If it's priority 1 (fix for next beta/patch release build) and it was found in 5.2.0, so why it's not fixed in 5.2.1?
retraffic
Sep 27, 2015 12:26
How can this not be a number one priority?
This issue potentially breaks any Unity project with a Mac build that uses keyboard input.
zbyhoo
Sep 26, 2015 09:26
Is there any workaround for this issue at this time? (unity 5.2.1)
drizzlybear
Sep 26, 2015 00:33
is there a workaround for this, or are we just waiting for a fix?
bitbutter
Sep 25, 2015 19:54
Lost a couple of hours to this just now. Frustrating.
Selosoft
Sep 25, 2015 18:41
Just downloaded 5.2.1 p1. still broken... It's obvious this isn't a priority at this point. I have no choice to revert to Unity 5.1 now as progress is dependent on this issue being fixed. I'm going to file bug reports and email everyone I can to get some sort of answer though!
edwin_mindcandy
Sep 24, 2015 11:25
Yep, I can confirm that this is still broke in 5.2.1.
Selosoft
Sep 23, 2015 01:11
Yup, broken still, even with latest version of Unity 5.2.1 it still doesn't work.