Search Issue Tracker
Fixed in 1.5.0 & 2.1.0
Votes
1
Found in [Package]
2.0.1
Issue ID
1174051
Regression
No
[TextMesh Pro] Inconsistant .SetText() behaviour between Play Mode and Standalone Build
How to reproduce:
1. Open the attached project named Case_1174051
2. Enter Play mode and click the button to start the test
3. Observe that text fields have changed into "- Clicked"
4. Build and Run the project
5. Star the test in the Build
6. Observe the change in the text fields
Expected result: Text fields behave the same way as in Play mode
Actual result: One of the Text fields that have used SetText() receives a different value in the Build
Reproducible with: 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a11
Could not test with: 2017.4.31f1(No Package Manager)
Package versions tested: 1.1.0, 1.2.4, 1.3.0, 1.4.1, 2.0.1
Comments (1)
-
SimDevs
Sep 01, 2019 07:45
Experiencing the same behavior in 2018.4.8f1
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
- 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
Resolution Note (fix version 1.5.0 & 2.1.0):
The following issue has been resolved. The fix will be included in the next release of the TMP package which will be version 1.5.0 for Unity 2018.4 and 2.1.0 for Unity 2019.x.