Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a10
2019.2.0a1
2019.3.0a1
2019.3.0a7
Issue ID
1164482
Regression
Yes
[UWP] The exception is thrown when selecting TMP input field in Debug Build
Steps to reproduce:
1. Download 1164482_repro.zip
2. Switch platform to UWP
3. Build SampleScene
4. Open VS solution and build project (debug, x64, Local Machine)
5. Select TMP InputField
Results: Exception is thrown.
Reproduced with: 2019.3.0a7, 2019.2.0b7, 2019.1.8f1
Not reproducible with: 2018.4.3f1
Regression introduced in: 2019.1.0a10
Reproduce with TMP versions: 1.3.0, 2.0.1
Note:
- Not reproducible with Release and Master builds
- Selecting first Standart InputField and then TMP InputField doesn't reproduce this issue
Exception:
TextInputController isn't initialized!
UnityEngine.TouchScreenKeyboard:get_text()
UnityEngine.TouchScreenKeyboard:set_selection(RangeInt)
TMPro.TMP_InputField:ActivateInputFieldInternal()
TMPro.TMP_InputField:LateUpdate()
Comments (1)
-
Arrovs
Oct 26, 2019 22:09
2019.2.10 have this problem. And it makes caret jump 2 chars instead of one and also deletes 2. Its annoying and that is not enough just to remove error.
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
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
- Last segment of a Sprite Shape Spline is affected by other segments' Sprite Variant change when no edge Sprite is selected
Resolution Note (fix version 2019.3):
The error(s) are DebugAsserts that were fired due to a race condition during initialization of the UWP SoftwareKeyboard; initialization must occur on the Windows UI thread instead of the "Game Loop" thread.
However, the scenario didn't result in any bad behavior or other malfunctions other that triggering this message, i.e. the asserts were benign, and since there's nothing the developer can do about it, these asserts were removed.