Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2023.1.9f1
Votes
0
Found in
2021.3.29f1
2023.1.7f1
Issue ID
UUM-44347
Regression
Yes
AssetImportWorkers are stuck indefinitely at "Android Extension - Scanning For ADB Devices" when exporting packages in batchmode with no graphics
Reproduction steps:
1. Ensure the Editor has the Android Support module
2. Download and unzip the “WorkerFreeze_Stripped“ project
3. Ensure the project has no Library
4. Run the following command in Terminal: PATH_TO_UNITY -batchmode -quit -projectPath PATH_TO_PROJECT -executeMethod PackageExporter.ExportProject -nographics
5. Observe the logs in the Terminal
Expected result: The batchmode is exited successfully
Actual result: The Editor is stuck indefinitely at “Starting new worker” or “Worker ready: AssetImportWorker”
Regressed in: 2021.3.23f1
Already fixed in: 2022.3.5f1, 2023.2.0a22
Reproduced in: 2021.3.23f1, 2021.3.29f1, 2022.3.4f1, 2023.1.6f1, 2023.1.7f1, 2023.2.0a21
Not reproduced in: 2021.3.22f1, 2022.3.5f1, 2022.3.6f1, 2023.2.0a22, 2023.2.0b3
Reproduced using: macOS 13.4.1 (c) (Intel)
The last few logs:
Starting new worker id: 0 with log in
Starting new worker id: 1 with log in
Worker ready: AssetImportWorker1 1
Worker ready: AssetImportWorker0 0
Based on AssetImportWorker logs, the workers get stuck at:
Android Extension - Scanning For ADB Devices 390 ms
Attempted to call .Dispose on an already disposed CancellationTokenSource
Android Extension - Scanning For ADB Devices 408 ms
Example command: /Applications/Unity/2021.3.23f1_213b516bf396_x64/Unity.app/Contents/MacOS/Unity -batchmode -quit -projectPath /Users/ainis/Downloads/WorkerFreeze_Stripped -executeMethod PackageExporter.ExportProject -nographics
Note: Similar to [https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-41796] which was fixed in 2023.2.0a21
Comments (3)
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
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
havokentity
Mar 18, 2025 12:50
This issue is there in Unity 6000.0.40 till 42 in the regular (Not no graphics mode) that I've tested and it's driving me insane.
VeryHappyYoung
Mar 07, 2024 12:05
Hello.
Would you be able to try not passing -nographics as a parameter? (removing the -nographics) That was what my coworker did.
Thank you.
ProZ-BHGS
Mar 07, 2024 01:28
Do you have any workaround about this issue? For some reason I must use Unity 2022.3.1f1 Editor which has this issue