Search Issue Tracker
Fixed in 3.0.0-preview.3
Votes
5
Found in [Package]
3.0.0-preview.1
Issue ID
1203865
Regression
Yes
TextMeshPro Input Field throws errors in Play Mode
How to reproduce:
1. Open attached project "Case_1203865" and load "SampleScene"
2. Open the Console window and enter Play Mode
3. Observe the Console window
Expected result: no errors are thrown
Actual result: errors are thrown upon entering Play Mode:
"MissingComponentException: There is no 'CanvasRenderer' attached to the "Caret" game object, but a script is trying to access it.
You probably need to add a CanvasRenderer to the game object "Caret". Or your script needs to check if the component is attached before using it."
Reproducible with: TMP 3.0.0-preview.1 (Unity 2020.1.0a15, 2020.1.0a16)
Not reproducible with: TMP 1.4.1 (2018.4.14f1), 2.1.0-preview.2 (2019.2.16f1, 2019.3.0f2, 2020.1.0a14)
Could not test with: Unity 2017.4.35f1 (no package)
Notes: Although the error concerns the "Caret" GameObject, the errors only stop if you disable the "Text Area" GameObject and not the "Caret" GameObject
Comments (5)
-
melkior
May 01, 2020 16:21
I am experiencing the same issue on 2020.2.0a9 and 2020.2.0a8 . Similar to KTHROSE when I disable the TMP input fields at runtime then the error goes away.
When updating to TMP preview version 3.0.0-preview.11 resolved for me.
-
kthrose
Apr 18, 2020 14:49
Sorry! I meant it appeared in preview1 3.3.0. I wasn't able to download preview3, I skipped right to 8.
-
kthrose
Apr 18, 2020 14:48
I can confirm this error did appear in preview.3 3.3.0 and was resolved when I downloaded preview.8. In my case, I was using a UI Panel and UI Dropdown without any trouble - then, I added TMP Input Field, and it caused this error on play. As per the reporter, I was able to to make it go away by deactivating it in the hierarchy.
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
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Resolution Note (fix version 3.0.0-preview.3):
Fixed in package version preview.3 - 3.0.0