Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.2.2f1
2018.4
2019.4
2020.1
2020.2
2021.1
2021.2
Issue ID
1056069
Regression
No
AssetBundle does not get updated in the Editor when removing the assetBundleName line from the meta file of an Asset
How to reproduce:
1. Create a new project
2. In the Project window create a new Material and select it
3. In the Inspector window create a new AssetBundle
4. Open the meta file of the created material Asset in an external editor and remove the line which starts with 'assetBundleName: '
5. Assign the material to the same AssetBundle one more time
6. Repeat step 4
Expected result: the Asset isn't assigned to the earlier created AssetBundle
Actual result: the Asset is still assigned to the AssetBundle
Reproducible with: 2018.4.31f1, 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1, 2021.2.0a1
Notes:
- Last two steps are unnecessary for 2018.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment