Search Issue Tracker
Fixed in 2020.2.X
Votes
2
Found in
2019.3.0a1
2019.3.0f6
2020.1
2020.2
Issue ID
1223834
Regression
Yes
AssetDatabase.AddObjectToAsset sets objectToAdd as the base asset when its name is same as the assetObject
How to reproduce:
1. Open the attached project
2. In the Assets/Create tab, click on "Asset A with Sub-Asset B" option
3. In the Project Window, go to the Assets folder
4. Inspect the "TestAsset"
Expected result: Base asset is "TestAssetA" and the Sub-Asset is "TestAssetB"
Actual result: Base asset is "TestAssetB" and the Sub-Asset is "TestAssetA"
Reproducible with: 2019.3.0a1, 2019.3.4f1, 2020.1.0a26, 2020.2.0a1
Not reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.2.21f1
Comments (1)
-
SamTechArt
Mar 06, 2020 14:56
I have the same problem, it's quite annoying, I haven't found a clean way to get around it except go back to version 1 of the Asset Pipeline.
There are also some general refresh problems on the sub-assets that can only be fixed with an application switch. The classic refresh functions don't work on them anymore.
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
- XR Device Simulator - Hands reset causes them to fly away
- Sprites is not rendered in a SRP Batcher when Sprite Mask is removed after it was previously set
- Crash on MemoryProfiler::GetAllocationRoot when entering Play mode on a specific project
- Video Player preview is not shown when Inspector preview is converted to Floating Window
- Invalid signature package console message is not visible after package import when Console has 'Clear on Recompile' setting enabled
Resolution Note (fix version 2020.2):
Fixed in Unity 2021.1.0a8 and above