Search Issue Tracker
Fixed in 1.5.1-preview
Votes
0
Found in [Package]
2018.4.0f1
2018.4.2f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1165898
Regression
No
[Scriptable Build Pipeline] CompatibilityAssetBundleManifest.ToString() generates malformed manifest file
How to reproduce:
1. Open attached project "Edited.zip"
2. Run the menu item: Test -> Old Style Build
3. Run the menu item: Test -> New Style Build
4. Open AssetBundles_OldStyleBuild/AssetBundles_OldStyleBuild.manifest file in a text editor to see how a manifest file should look
5. Compare AssetBundles_NewStyleBuild/AssetBundles_NewStyleBuild.manifest file to the previously formed one
Expected result: All the dependencies are being proceeded by a line containing "Dependencies:"
Actual result: All the dependencies are on the same line on(i.e line 8 in the attached picture) instead of being on a separate line each
Reproducible with: 2018.4.3f1, 2019.1.8f1, 2019.2.0b8, 2019.3.0a8
Couldn't test reliably on 2017.4 dues to the namespace errors:
Assets/Editor/BuildScript.cs(2,19): error CS0234: The type or namespace name `Build' does not exist in the namespace `UnityEngine'. Are you missing an assembly reference?
Assets/Editor/BuildScript.cs(2,19): error CS0234: The type or namespace name `Build' does not exist in the namespace `UnityEngine'. Are you missing an assembly reference?
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 not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
- A particle is not rendered for the first frame when the duration and lifetime values match
Add comment