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
- 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
Add comment