Search Issue Tracker
Fixed
Votes
0
Found in
2022.3.4f1
2023.1.3f1
Issue ID
UUM-41796
Regression
Yes
Command Line Builds hang on "Worker ready: AssetImportWorker"
How to reproduce:
1. Unarchive the “IN-45463” project
2. Open the Terminal and run {{sudo /Applications/Unity/[UnityVersion]/Unity.app/Contents/MacOS/Unity -ProjectPath ["IN-45463" project path] -batchmode -nographics -quit -executeMethod TestBuild.Run}}
3. Observe the Terminal
Expected result: The execution is finished with “Exiting batchmode successfully now!” message
Actual result: The execution hangs after “Worker ready: AssetImportWorker0 0”
Reproducible with: 2022.2.14f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a20
Not reproducible with: 2021.3.28f1, 2022.2.13f1, 2023.2.0a23
Fixed in: 2023.2.0a21
Testing environment: macOS 13.4.1 (M1), macOS 13.2.1 (Intel)
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
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is thrown when launching a project with a corrupted library
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-44347