Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
2
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a20
2023.3.0a3
Issue ID
UUM-40833
Regression
No
Child GameObject values are differently arranged in the Player if the "FindGameObjectsWithTag" method is used to locate them
How to reproduce:
1. Open the "IN_44951" project
2. Enter the Play Mode
3. Remember how numbers are arranged in Game View
4. Exit the Play Mode
5. Press File → Build And Run
6. Observe the Player
Expected result: numbers arrangement in the Game View and the Player are the same
Actual result: numbers arrangement in the Game View and the Player are different
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a20
Reproducible on: Windows 10 Pro
Notes:
- In 2023.2.0a20 numbers are arranged randomly in Editor and Player
- Not reproducible in the Editor
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
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
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.