Search Issue Tracker
Fixed
Votes
0
Found in
4.3.0f4
Issue ID
575555
Regression
Yes
Custom UnityActivity's on Android don't get any "keyDispatchEvent" or "onKeyDown" callbacks
This is a regression from Unity 4.2.
Reproduced on:
Google Nexus 4 (Android 4.3)
Input was sent with:
Nyko Playpad bluetooth controller
Reproduced with:
Unity Version 4.3.0f4 (e01000627d60)
Resolution:
The java path for input events has been deprecated for now. Events can still be injected into the engine using the functions on the UnityPlayer class but all os input is being polled in native using the native input queue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment