Search Issue Tracker
Fixed in 2018.1.X
Votes
6
Found in
5.6.2f1
Issue ID
958249
Regression
No
[AssetBundle] AssetBundle Hashes: AssetFileHash: Hash is not changed after AssetBundle binary changes
Script referred to Prefab in AssetBundle is renamed. AssetBundle binary changes but AssetBundle hash is unchanged.
Reproduction steps:
1) Open the attached project (RenameReferencedScript_DoesNotAffect_AssetBundleHash.zip).
2) Click Build>BuildAssetBundles on the top menu bar
3) Observe the file Build\AssetBundleBuild\testassetbundle.manifest and Build\AssetBundleBuild\testassetbundle
4) Rename the file MyBehaviour to MyBehaviourRenamed
5) Open MyBehaviourRenamed.cs and rename the class MyBehaviour to MyBehaviourRenamed
6) Click Build>BuildAssetBundles on the top menu bar again
7) Observe the file Build\AssetBundleBuild\testassetbundle.manifest and Build\AssetBundleBuild\testassetbundle
Actual behavior:
- Hashes: AssetFileHash: Hash: does not change in Build\AssetBundleBuild\testassetbundle.manifest
- Build\AssetBundleBuild\testassetbundle.manifest changes
Expected behavior:
- Hashes: AssetFileHash: Hash: changes in Build\AssetBundleBuild\testassetbundle.manifest
- Build\AssetBundleBuild\testassetbundle.manifest changes
Reproduced with: 2017.3.0b3, 5.6.3p4.
Comments (2)
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
ForceMagic
Aug 23, 2018 16:54
And I'm still having the same issue.
ForceMagic
Aug 23, 2018 16:54
I don't see any Release notes from 2018.1 (from 2018.1.0 to 2018.1.9) that reference that Fix ID.