Search Issue Tracker
Active
Under Consideration for 6000.2.X, 6000.3.X, 6000.4.X
Votes
1
Found in
6000.1.0a9
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
7000.0.0a1
Issue ID
UUM-91834
Regression
No
TMP_Text.text returns the initial value instead of the updated text when accessing text assigned using SetText functions multiple times
How to reproduce:
1. Open the attached “IN-90728” project
2. Build and run the project
3. Navigate to C:\Users\<Username>\AppData\LocalLow\DefaultCompany\broken_tmp_pro_repro and open the Player.log text document
4. Observe the “Assign text through …” sections in the text document
Expected result: Each section consistently displays the correct assigned text ("Test0" five times, "Test1" five times, "Test2" five times, and "Test3" five times)
Actual result: Only the first iteration of each section displays the correct value ("Test1", "Test2", "Test3") while subsequent iterations incorrectly display "Test0"
Reproducible with: 2021.3.47f1, 2022.3.55f1, 6000.0.32f1, 6000.1.0a9
Reproduced on: Windows 10, Windows 11, macOS
Not reproduced on: No other environments tested
Note: TMP_Text.SetText(string) works as intended, however, passing other arguments causes TMP_Text.text to return the initial value instead of the updated text when accessed multiple times
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment