Search Issue Tracker
Fixed in 4.1.X
Votes
0
Found in
3.2.0b2
Issue ID
387712
Regression
No
iOS mode editor handles textfield input inconsistently
The editor uses TTF text rendering in all modes, but the iOS runtime uses bitmap text rendering. This means that you can input non-ascii letters in textfields from an editor in iOS mode, but on an iOS runtime you can't by default (need to use a custom font for that).
The editor in iOS mode should work the same as the iOS runtime in this regard.
Steps:
- Create a project with a monobehaviour on a GO with a GUI method just handling a textfield.
- Enter playmode.
- Enter some non-ascii characters.
- Observe how this works just fine.
- Build and run the same scene on an iOS device.
- Enter some non-ascii characters.
- Observe how this fails.
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
Add comment