Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Found in [Package]
HoloLens2 - Using TouchScreenKeyboardType.EmailAddress to bring up the HoloLens system keyboard prevents JP IME from working
1. What happened
Follow the documentation here to bring up the system keyboard on HoloLens 2:
However, instead of using TouchScreenKeyboardType.Default, configure it to be TouchScreenKeyboardType.EmailAddress. On Japanese (language/keyboard, etc), even after switching input mode, the Japanese IME is still not showing up.
2. How we can reproduce it using the example you attached
a. Configure the device to use Japanese:
- Windows Display Language – Japanese
- App Preferred Language – Japanese
- Keyboard – Japanese Microsoft IME
b. Launch the app and then navigate to the "Unity UI Examples" and tap on the "UGUI Input Field (experimental)" to bring up the system keyboard.
c. Make sure the Japanese keyboard is selected and switch the system keyboard input mode to enter japanese char (2nd key on the bottom row of the keyboard from the left), e.g. it should read "abc".
d. Type 'ab' - the 'auto complete' of the keyboard only shows 'ab' and that's wha
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- IL2CPP Player crash on memset in VCRUNTIME140D when selecting UI GameObject
- [BiRP] GetScriptableCullingParameters() uses the wrong projection matrix when rendering two forward+ passes in XR
- Texture becomes lower quality when the texture is downloaded with script
- [tvOS] Multiple warnings in the Console when building for tvOS Platform on Intel Macbook
- [Android][Vulkan] Shader is rendered incorrectly in the Player when using Vulkan Graphics API