Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.22.2
2.2.2
Issue ID
ADDR-3749
Regression
No
'UnityEditor.Build.Pipeline.Utilities.ScriptableBuildPipeline' throws an exception when building Addressables
How to reproduce:
1. Open the “IN-83132_repro“ project
2. Navigate to Window → Asset Management → Addressables → Groups
3. In the Addressables Groups window, press Build → New Build → Default Build Script
4. Observe the Console
Expected result: Addressable build fails and errors are thrown
Actual result: Addressable build is successful
Reproducible with: 2.2.2 (6000.0.17f1), 1.22.2 (2023.2.20f1)
Could not test with: 2021.3.43f1, 2022.3.44f1 (unsupported asynchronous API)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Error:
The type initializer for 'UnityEditor.Build.Pipeline.Utilities.ScriptableBuildPipeline' threw an exception.
UnityEditor.GenericMenu:CatchMenu (object,string[],int)
Comments (1)
-
PaulMDev
Dec 21, 2024 22:45
Fixed by deleting `ScriptableBuildPipeline.json`.
I wish Unity told me what file was causing the issue, I spent a long time debugging to find this.
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
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.