Search Issue Tracker
Fixed in 2019.3.X
Votes
1
Found in
2019.3.0a7
2020.1.0a1
Issue ID
1179390
Regression
Yes
[Scripting] EditorUtility.CollectDependencies always returns null
The Unity scripting API EditorUtility.CollectDependencies() always returns null and doesn't function at all.
How to reproduce:
1. Open tester-attached project (CollectDependencies)
2. From the menu bar select BUG > Collect Dependencies
Expected result: dependencies are collected successfully
Actual result: a message stating that dependencies returned null is logged in the Console
Reproducible with: 2019.3.0a7, 2019.3.0b1, 2020.1.0a1
Not reproducible with: 2017.4.32f1, 2018.4.7f1, 2019.2.3f1, 2019.3.0a6
Comments (1)
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
- UI Builder windows text rendering breaks when using Rich text combined with an underlined emoji
- [Linux] Crash on mono_runtime_invoke when executing a specific script
- Installing the HDRP Water Samples doesn't notify the user to enable the "Water" on HDRP Asset
- Persistent Memory Leak in `ChunkDrawCommandOutput` and `CullingSplits.InitializeSplits`
- 1 KB or more of GC is allocated when Debug logging
julian-moschuering
Sep 09, 2019 08:56
For anyone interested: Workaround using the new API's:
https://gist.github.com/ArchyInf/c3917efc905a4be3c521eddc8cd5414f
Note: GetTypeDB must be cached as it executes a compilation step for the standalone libraries which takes some time.