Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2018.4.X, 2019.4.X, 2020.2.X
Votes
1
Found in
2018.3.0a6
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a12
2020.1.0a1
Issue ID
1178737
Regression
No
Assets used in components of a nested Prefab are counted as direct dependencies of all higher level nested Prefabs
Note: This issue shows a bug in our AssetDatabase.GetDependencies(someFiles, false); (calculating direct dependencies)
How to reproduce:
1. Open user's attached project ("BuildAssetBundles.zip") using the EnvIronman VM (more information in Edit)
2. Select A Prefab in the Project window
3. Select direct dependencies of the A Prefab (Right mouse click -> Select Direct Dependencies)
Expected result: Only B Prefab is selected as a direct dependency
Actual Result: B Prefab and Assets used in Prefab C's components are selected as direct dependencies
Reproducible with: 2018.4.7f1, 2019.1.14f1, 2019.2.3f1, 2019.3.0b1, 2020.1.0a1
Notes:
The issue was not reproducible until nested Prefabs were introduced in 2018.3.0a6.
The issue can be reproduced using Prefab variants as well.
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
- Scene is brighter in Standalone player if it was open in the Editor at build time
- [Android] APP becomes unresponsive and crashes with ANR errors
- Replace no longer replaces when using incremental pipeline
- [LightProbes] Individual light probe gizmos are no longer visible
- Input.GetKey() returns true for Alt key after Alt+Tabbing and reopening Build during Coroutine
Resolution Note (fix version 2021.1):
Nested prefabs are baking in the nestee prefabs, so all their direct runtime dependencies are also a direct runtime dependencies of the nesting prefab.
The behavior described in the bug is actually a new feature request.