Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
5.5.2f1
Issue ID
1038830
Regression
Yes
Different asset bundles produced after building them two times in a row
How to reproduce:
1. Open attached Unity project "zProject_486458"
2. Switch platform to iOS
3. Select BuildTools --> Build AssetBundles
4. Wait until bundles are build
5. Open command-line
6. Run WebExtract <FilePathToSceneBundle>
7. Run binary2text YourSceneBundleName_data/BuildPlayer-SceneBundleName
8. Make a copy of a created text file
9. Close Unity Editor
10. Clear Library and AssetBundles folders
11. Repeat 1-7 steps
12. Compare bundles
Expected result: builds should be identical.
Actual result: builds have differences.
Reproduced with: 2018.1.5f1, 2017.4.5f1, 2017.2.3p1, 5.5.6f1.
Not reproduced with: 2018.3.0a1, 2018.2.0b8, 2017.1.4p1, 5.6.6f2.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment