Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2023.2.0a15
2023.3.0a14
Issue ID
UUM-55749
Regression
Yes
User gets an error "MissingReferenceException: The object of type 'UnityEditor.DockArea' has been destroyed but you are still trying to access it."
Steps to reproduce:
- Create a project;
- Go to the menu "Window" -> "Text";
- Select "Sprite Importer"
- Verify that the "Sprite Importer" popup becomes visible;
- Click the kebab menu and verify that the contextual menu becomes visible;
- Close the "Sprite Importer" window;
- Observe that the contextual menu stays on the screen;
- In the contextual menu, which is still displayed, select "Add Tab" -> "Scene";
- Observe the "Console" window.
Expected Result: When the user closes the "Sprite Importer" popup contextual menu should be removed too. Any errors in the Console.
Actual Result: The console displays an error "MissingReferenceException: The object of type 'UnityEditor.DockArea' has been destroyed but you are still trying to access it.
Your script should either check if it is null or you should not destroy the object." Added screenshot in the "Attachments" section.
Reproducible with: 2023.2.0a15, 2023.2.0b18, 2023.3.0a14.
Not reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.19f1, 2023.2.0a14.
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Due to the state of the new Contextual Menus feature, we decided to revert to OS Menus in 2023.3. Hence, we are cancelling all 2023.2.X ports and recommend using 2023.3.0b1 or higher for more stable context menus. The feature will be reconsidered in future versions.
Resolution Note (2023.3.X):
Due to the state of the new Contextual Menus feature, we decided to revert to OS Menus in 2023.3. Hence, we are cancelling all 2023.2.X ports and recommend using 2023.3.0b1 or higher for more stable context menus. The feature will be reconsidered in future versions.