Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0a6
2018.3.0b5
Issue ID
1090852
Regression
Yes
[Regression] Changing AssetImporter.assetBundleName sometimes fails
How to reproduce:
1. Open the user-submitted project ("AssetBundleNameBug.zip")
2. Click "Tools" -> "Define Asset Bundle Name With Folder Name"
3. Observe the console errors
Expected result: The Asset bundle names are correctly assigned
Actual result: AssetImporter.assetBundleName fails in some instances
Reproduced in: 2019.1.0a5, 2018.3.0b6, 2018.2.12f1, 2018.2.0a6
Not reproducible in: 2018.2.0a3, 2018.1.9f2, 2017.4.13f1
Couldn't test with: 2018.2.0b2; 2018.2.0a5; 2018.2.0a4 (Project crashes on launch)
Note: "Define Asset Bundle Name With Value Test To Children" method, works for some assets but not for all
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment