Search Issue Tracker
Fixed
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a8
2020.1.0b9
2020.2.0a1
Issue ID
1249167
Regression
Yes
Custom Editor of a ScriptableObject gets destroyed when renaming a Sub Asset while the Tile Palette window is open
How to reproduce:
1. Open the attached "ImportAssetBug" project
2. Open Tile Pallete window from Window > 2D > Tile Palette
3. Select "TestAsset.asset" from the Assets folder
4. Double click on "Element 0" called "Test 5" in the Inspector window
5. Change the "Name" field value to "Test 6" and hit Enter
Expected result: the custom Editor remains open and no errors are thrown
Actual result: the custom Editor gets destroyed, reopened and a "NullReferenceException" error is thrown
Reproducible with: 2020.1.0a8, 2020.1.0b10, 2020.2.0a1, 2020.2.0a3
Not reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0a7, 2020.2.0a4, 2020.2.0a11
Notes:
-This reproduces with AssetDatabase.SaveAssets and AssetDatabase.ImportAsset methods in the Custom Editor Script
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
- Different text alignment in the column header in Entities "System" window
- 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
Resolution Note:
Fixed in 2020.2.0a4
Resolution Note (fix version 2020.1):
Fixed in 2020.1.4f1