Search Issue Tracker
Fixed in 1.5.0 & 2.1.0
Votes
0
Found in [Package]
1.4.1
Issue ID
1176674
Regression
No
[Mobile] TextMeshPro - InputField doesn't open the keyboard on click if "Content Type" is set to "Custom"
How to reproduce:
1. Build the "TMP_repro.zip" project for iOS
2. Build & Run the app on a device via Xcode
3. Press on the Input Field
Actual result: Keyboard doesn't come up after pressing on the Input Field.
Expected result: Keyboard comes up after pressing on the Input Field.
Reproducible with: 2020.1.0a1, 2019.3.0b1, 2019.2.3f1, 2018.4.7f1.
Devices reproducible with:
- iPhone 7 (iOS 10.2)
- iPhone 8 Plus (iOS 12.0)
- VLNQA00272, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Notes:
- TextMeshPro is not implemented in Unity 2017.4.
- Reproducible on both iOS and Android.
- The issue reproduces when Input Field's "Content Type" is set to "Custom"
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.5.0 & 2.1.0):
This issue was previously reported (on the Unity Forum) and has been addressed. The fix will be included in the next release of the TMP package which will be version 1.5.0 for Unity 2018.4 and 2.1.0 for Unity 2019.x.