Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
7
Found in
2020.3
2020.3.11f1
2021.1
2021.2
2022.1
Issue ID
1357414
Regression
No
Crash on BuildPipeline::WriteSceneSerializedFile when building Addressable content
How to reproduce:
1. Open the attached "1357414.zip" project
2. Go to Window -> Asset Management -> Addressables -> Groups
3. In the Addressables Groups window go to Build -> New Build -> Default Build Script
Expected result: Addressable content successfully built
Actual result: The Editor crashes
Reproducible with: 1.19.0, 1.19.1, 1.19.2 (2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a6)
Couldn't test with: 1.19.2 (2019.4.30f1) (Compilation errors after downgrade)
First lines of the stacktrace:
0x00007ff799205834 (Unity) BuildPipeline::WriteSceneSerializedFile
0x00007ff7998041c6 (Unity) BuildPipeline::WriteSceneSerializedFile_Internal
0x00007ff79970f6f3 (Unity) ContentBuildInterface_CUSTOM_WriteSceneSerializedFile_Internal_Injected
Comments (1)
-
MikeHergaarden
Oct 13, 2021 14:42
Still an issue for us too and significantly impacting development time.
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2):
Fixed edge case passing in missing or deleted objects could crash the Editor during the build.
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b6
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.16f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.33f1