Search Issue Tracker
Won't Fix
Under Consideration for 6000.0.X
Votes
0
Found in
6000.0.14f1
7000.0.0a1
Issue ID
UUM-77830
Regression
Yes
Debug.Log does not print the number in the string when the number is "24"
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/Scenes/SampleScene“ scene
3. Enter Play Mode
4. Observe the Console window
Expected result: Debug.Log with the number 24 is logged
Actual result: The Debug.Log does not have the number 24
Reproducible with: 2023.1.0a20, 6000.0.14f1
Not reproducible with: 2021.3.42f1, 2022.3.41f1, 2023.1.0a19
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note:
To improve performance, rich text tags are converted to hash codes. In this case, the issue arises from a collision between the tags <24> and </i>.
This behavior is expected with rich text. There are a couple of workarounds, such as using the <noparse> tag in a rich text label or disabling rich text altogether.
Given the available workarounds and the low impact of this issue, we’ve decided to close the bug and will not be prioritizing it at this time.