Search Issue Tracker
Active
Votes
0
Found in
2.9.1
Issue ID
UUM-136150
Regression
Yes
Addressables build fails when "ADDRESSABLES_ADD_DEFINES" is added to Scripting Define Symbols
How to reproduce:
1. Open the attached project “IN-136173”
2. Open the Addressables Groups window
3. In the Addressables Groups window, select “Build → New Build → Default Build Script”
4. Observe the Console
Actual result: Addressable content build fails and more than 60 errors are thrown from the Collections package
Expected result: Addressable content build succeeds
Reproducible with: 2.9.0 (6000.5.0a8), 2.9.1 (6000.5.0a8)
Not reproducible with: 2.8.1 (6000.5.0a8)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Example of an error message that is thrown: “Library\PackageCache\com.unity.collections@32dc8bfa8d72\Unity.Collections\NativeParallelMultiHashMap.cs(659,13): error CS0246: The type or namespace name 'AtomicSafetyHandle' could not be found”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment