Search Issue Tracker
Fixed in 1.17.4-preview
Votes
0
Found in [Package]
2019.4
2020.3
2021.1
2021.1.3f1
2021.2
Issue ID
1334588
Regression
No
[Addressables][IL2CPP] error at Unity.IL2CPP.HashCodeCache`1.GetUniqueHash(T value) when building on Android
Reproduction steps:
1. Open the attached project
2. Build on Android
Expected result: The project builds successfully
Actual result: The build fails due to this error: Unity.IL2CPP.HashCodeCollisionException: Hash code collision on value `2A6D185FEED8AA52CD66C11FEEC199E7324C007A`
Not reproducible with: 1.15.1 - 1.18.4 (2021.2.0a11 - 2021.2.0a18)
Not reproducible with: 1.17.4-preview - 1.18.4 (2019.4.28f1, 2020.3.9f1, 2021.1.9f1, 2021.2.0a10)
Reproducible with: 1.15.1 - 1.17.2-preview (2019.4.28f1, 2020.3.9f1, 2021.1.9f1, 2021.2.0a18)
Can't test with: 2018.4.35f1 - PrecompiledAssemblyException: Multiple precompiled assemblies with the same name nunit.framework.dll included or the current platform
Notes:
- Does not reproduce when building on Standalone
- Does not reproduce with Mono
- Does not reproduce if the "BGDatabaseAddressables" folder is deleted
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
Add comment