Search Issue Tracker
Active
Under Consideration for 6000.7.X
Votes
0
Found in
6000.0.69f1
6000.3.10f1
6000.4.0b9
6000.5.0a8
6000.6.0a2
6000.7.0a1
Issue ID
UUM-137164
Regression
Yes
Text input fields not working when using Android with Bluetooth Keyboard
Steps to reproduce:
1. Open the attached project “IN-135771”
2. Build and run on Android
3. Connect Bluetooth keyboard to your Android device
4. Try both typing into both fields that appear in the screen
Actual result: From time to time the keyboard doesn’t type anything, sometimes it types one letter and stops working
Expected result: The keyboard works every time and is able to type in both fields
Reproducible with: 6000.0.42f1, 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a8
Not reproducible with: 6000.0.41f1
Built on: macOS Tahoe 26.3 (25D125)
Reproducible with these devices:
VLNQA00531 - OnePlus OnePlus 11 5G (CPH2449), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 13
VLNQA00367 - Galaxy Z Fold2 5G (SM-F916B), CPU: Snapdragon 865 SM8250, GPU: Adreno 650, OS: 10
Not reproducible with these devices
VLNQA00319 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 13
Notes:
- Very inconsistent reproduction, heavily depends on the version of the Unity editor and the device
- Galaxy Z Fold2 had an issue mainly with 6000.0, 6000.4, 6000.5. The on-screen keyboard opens for a brief second and as you type on the physical keyboard on key appears in the field and stops responding
- OnePlus mostly worked with the Bluetooth keyboard. There were a couple cases when it failed to register the keystrokes. Usually reloading the project fixes the issues.
- I used the Apples magic keyboard with numeric keypad for testing
- None of these input fields work: TextMeshPro, UI builder, Legacy
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Add comment