Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
920288
Regression
No
Having two scenes with the same filename in one bundle would cause errors when building the bundle (Fix suggested)
Open the attached project:
1. Open the attached project.
2. Go to Bundles > Build.
3. Check the Console:
Assertion failed: Assertion failed on expression: 'srcFileInfo.temporaryObjectIdentifier.localIdentifierInFile == localIdentifierInFile'
UnityEditor.BuildPipeline:BuildAssetBundles(String, BuildAssetBundleOptions, BuildTarget)
Reproduced with:
5.5.0f1, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
Notes:
- To avoid the issues go to Test > Run (Windows).
- Check the user patch (attached in this case) (1:50 AM).
- Full paths are always checked first to avoid a short name blocking a scene. For
example if you have in your build settings:
A/A.unity
A.unity
The latter couldn't be loaded. With this change, "A" will load the second, and only
"A/A" will load the first.
- Having two scenes with the same filename in one bundle would cause errors when
building the bundle.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment