Search Issue Tracker
Won't Fix
Votes
17
Found in
2022.2.7f1
2023.1.0b3
2023.2.0a2
Issue ID
UUM-27669
Regression
No
Unable to build asset bundle when using CalculateSceneDependencyData() method
Reproduction steps:
1. Open the “TestProject-With-AssetBundleBug” Project
2. Open the “Assets/Investments/01_OlimpiaPort.unity” Scene
3. In the top menu select Tools → BuildManager
4. In the “BUNDLES OVERVIEW” field select 01_OlimpiaPort → Scene → Build
Expected result: Asset bundle is built
Actual result: An error is thrown
Reproducible with: 2022.2.7f1, 2023.1.0b3, 2023.2.0a2
Could not test with:
2020.3.45f1 (error CS8124: Tuple must contain at least two elements.)
2021.3.18f1 (Build Manager tool is not available)
2022.1.24f1 (error CS0246: The type or namespace name 'VolumeProfile' could not be found (are you missing a using directive or an assembly reference?))
Reproduced on: Intel MacOS 13.1
-
thomas642daniel
Jul 15, 2024 07:23
It's very useful us but not allow in version 2022.2
-
yslab
Feb 21, 2023 07:47
I need this. It's no allow me to use version 2022.2. I can't build my project.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
The calls in the project code CalculateCommonBundles() do not match the calls in ScriptableBuildPipeline DefaultBuildTasks(). E.g. in that implementation CalculateSceneDependencyData is called directly after PostScriptsCallback. We are not able to help debug issues arising with custom implementations that extend the Scriptable Build Pipeline, as it is likely the bug is in the customer project. So it is recommended to compare with the default implementation and see if it is possible to more closely match its order of operations.