Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.12f1
2023.2.0b8
2023.3.0a4
Issue ID
UUM-47798
Regression
No
Asset Bundles do not detect dependencies in manifests when the dependencies are Scriptable Objects
How to reproduce:
1. Open the attached “WlkExposure.zip” Project
2. Press the “Test SO → Build bundles” button in the Tool Bar
3. Open the “StreamingAssets” folder in an explorer
4. Open any “*.manifest” file in the folder in a text editor
5. Observe the “Dependencies” section
Expected result: Dependencies exist and are listed
Actual result: No dependencies exist
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b8, 2023.3.0a4
Reproduced on: macOS Ventura 13.5 (Intel)
Not reproduced on: No other environment tested
Note: The user has noted that - “The inspection of the resulting asset bundles using Unity command-line tools (WebExtract + binary2text) shows that there is indeed a dependency”
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.