Search Issue Tracker
Won't Fix
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
- Scene view audio toggle doesn't work after disabling and enabling audio source component with audio random container
- Pitch changes while paused messes up scheduling of the audio random container
- Crash on detail::ComputeShaderSnippetKey when entering the Play mode
- Unable to interact with Material Inspector window when creating a new Material and renaming it
- Shadow artifact is cast onto GameObjects in the Scene view when the Scene view lighting is disabled
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.