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
- "Assertion failed on expression" errors appear when selecting specific Tile Palette GameObjects
- “CommandBuffer: built-in render texture type 3 not found while executing” warning is displayed in URP project
- Player build logs a "material with shader doesn't have a '_MainTex' property" error when instantiating a specific amount of specific prefabs
- The LayerMask parameter is ignored when using Physics2D.GetRayIntersection method
- The Tilemap GameObject causes other Tilemap GameObjects to become invisible when its “Mask Interaction” is set to “Visible Inside Mask”
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-44347