Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2022.3.25f1
6000.0.0b15
Issue ID
UUM-70139
Regression
No
Nullref in TMPro text on Standalone Build Shutdown
- What happened
Nullref in TMPro text on Standalone Build Shutdown
- How can we reproduce it using the example you attached
Easy Way:
- Fix path to unityExe on line 14 of RunRepro.py
- Run RunRepro.exe
You should see this output:
NullReferenceException at 0.2 minutes
at TMPro.TMP_SubMeshUI.UpdateMaterial () [0x00021] in .\Library\PackageCache\com.unity.textmeshpro@3.0.6\Scripts\Runtime\TMP_SubMeshUI.cs:710 at 0.2 minutes
at TMPro.TMP_SubMeshUI.SetMaterialDirty () [0x00007] in .\Library\PackageCache\com.unity.textmeshpro@3.0.6\Scripts\Runtime\TMP_SubMeshUI.cs:617 at 0.2 minutes
at TMPro.TMP_SubMeshUI.OnDisable () [0x00000] in .\Library\PackageCache\com.unity.textmeshpro@3.0.6\Scripts\Runtime\TMP_SubMeshUI.cs:286 at 0.2 minutes
which is a repro.
Slightly Less Easy Way:
- Load the project up
- Make a Standalone Build
- After you see the small text in the centre of the screen, press Alt+F4 to close the Standalone Build
- Load up C:\Users[username]\AppData\LocalLow\...\...\Player.log and check for NullReferenceException in TMPro.TMP_SubMeshUI.UpdateMaterial in the Player.log
Expected: no Null exception on shutdown of the game
Note: Skipped CQA testing.
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Please update to TMP 3.2.0. The bug is fixed in this version of TMP.
Resolution Note (6000.0.X):
Please update to TMP 3.2.0. The bug is fixed in this version of TMP.