Search Issue Tracker
Fixed
Fixed in 2022.3.61f1, 6000.0.42f1, 6000.1.0b10, 6000.2.0a7
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.24f1
6000.1.0a1
6000.2.0a1
Issue ID
UUM-85011
Regression
No
UI Builders incorrectly informs about a circular dependency when the reference in the second UI Document is removed
How to reproduce:
1. Create and open a new project
2. Create two UI Documents (“first“ and “second“)
3. Open the “first“ UI Document in UI Builder
4. Add and delete the reference to the “second“ UI Document in the UI Builder
5. Save the changes and then open the “second“ UI Document in UI Builder
6. Try referencing the “first“ UI Document in UI Builder
7. Observe the Editor
Expected result: The reference of the “second“ UI Document is successfully placed into the “first“ UI Document
Actual result: A circular dependency warning dialog box is invoked
Reproducible in: 2021.3.45f1, 2022.3.51f1, 6000.0.24f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- This persists even if the UI Builder is closed and reopened, only restarting the Editor will stop the circular dependency warnings
- The UI Builder probably does not lose the reference to previous elements or UI Documents
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Add comment