Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2021.3.34f1
2022.3.4f1
2022.3.19f1
2023.2.8f1
2023.3.0a16
2023.3.0b5
Issue ID
UUM-62992
Regression
No
"Localize String Event" Component's "Local Variables" have empty values when they are copied and pasted
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/SampleScene“ Scene
3. In the Hierarchy window, select “OriginalText” (Canvas > OriginalText) GameObject
4. In the Inspector window, open the context menu of “Localize String Event” Component’s “Local variables” variable and select “Copy”
5. In the Hierarchy window, select “CopyText” (Canvas > CopyText) GameObject
6. In the Inspector window, open the context menu of “Localize String Event” Component’s “Local variables” variable and select “Paste”
7. Observe the pasted variables
Expected result: The pasted variables' “string” value is the same as in the “OriginalText” GameObject
Actual result: The “string“ value is empty
Reproducible with: 1.3.2 (2021.3.34f1, 2022.3.4f1), 1.4.5 (2021.3.34f1, 2022.3.19f1, 2023.2.8f1, 2023.3.0a16), 1.5.0-pre.5 (2021.3.34f1, 2022.3.19f1, 2023.2.8f1, 2023.3.0b5)
Reproducible on: Windows 11, macOS 14.1.1 (M2 Max) (by user)
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
- 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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.