Search Issue Tracker
By Design
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.14f1
2023.1.0b11
2023.2.0a9
Issue ID
UUM-32236
Regression
No
[iOS] Capitalization in the keyboard is enabled when setting the Content Type of InputField to “Alphanumeric”
How to reproduce:
1. Build And Run the user’s attached “TestsKeyb2.zip” project
2. In the app, enable the “Password” checkbox
3. Focus text field and observe the onscreen keyboard
Expected result: Capitalization is turned off
Actual result: Capitalization is turned on
Reproducible with: 3.0.6 (2020.3.47f1, 2021.3.22f1, 2022.2.14f1), 4.0.0-pre.2 (2023.1.0b11 2023.2.0a9)
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Notes:
Not reproducible on iOS if the "Auto-Capitalisation" setting in Keyboard settings is turned off
Not reproducible on Android (user's info)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Keyboard respects device settings
iOS: General -> Keyboard -> Auto-Capitalisation
Android: System Settings > Keyboard & input method -> Gboard -> Text correct -> Auto-capitalization