Search Issue Tracker
Fixed
Fixed in 6000.0.72f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0a9, 6000.6.0a1
Votes
0
Found in
6000.0.66f1
6000.3.5f1
6000.4.0b5
6000.5.0a5
6000.6.0a1
Issue ID
UUM-132608
Regression
No
“Destroying assets is not permitted to avoid data loss” error thrown when creating a second Tile Palette Brush Pick Asset
Steps to reproduce:
1. Create new Unity project using Universal 2D Template
2. Open Preferences window
3. Select Tile Palette section
4. Find Brush Picks section
5. Press “New” button
6. Name it “BrushPick” and press Save
7. Back in Preferences, press “New” button to create new Brush
8. Name it “BrushPick1” and Save it
9. Observe Console window
Actual results: Error “Destroying assets is not permitted to avoid data loss.
If you really want to remove an asset use DestroyImmediate (theObject, true);
UnityEditor.GUIView:ProcessEvent (UnityEngine.EntityId,intptr,bool&)” is thrown in the Console window
Expected results: No errors thrown in the Console window
Reproducible with versions: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Tested on (OS): Windows 11, macOS Silicon Tahoe 26.2 (M1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.4.1f1):
Fixed in 6000.4.1f1
Resolution Note (fix version 6000.3.12f1):
Fixed in 6000.3.12f1
Resolution Note (fix version 6000.0.72f1):
Fixed in 6000.0.72f1