Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X
Votes
0
Found in
2019.1.0b2
2019.1.0b7
2019.2.0a1
Issue ID
1137073
Regression
Yes
Batchmode build hangs in PackageManager::RunRequestSynchronously
To reproduce:
1. Open attached project "demos_20191.zip"
2. Open project folder
3. Open "build.sh" file with any text editor
4. Change UNITYAPP= to your local Unity install folder
5. Save and run the file (e.g. using terminal with "sh" command: "sh /Users/*username*/Downloads/case_1137073-demos_20191/build.sh" )
Expected result: the project is built without any issues
Actual result: the build gets stuck at "Refresh: detecting if any assets need to be imported or removed ..."
Reproduced on:
2019.1.0b2(669ada05268b) 2019.2.0a10
Doesn't reproduce on:
2018.3.12f1 2019.1.0a1 2019.1.0b1
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
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
- ChangeSets are not detected when created via Editor Scripts
- "Cyclic Prefab nesting not supported" error window is thrown when trying to nest two sibling prefab variants
- BuildPipeline error is thrown when building Asset Bundles
- "IndexOutOfRangeException" errors appear when entering Play Mode if using "AsDeferredJobArray"
tudonca
Jul 31, 2019 22:46
I had the same issue on Unity 2018.4
I was able to fix this by manually calling AssetDatabase.Refresh() at the end of my build script, before Unity initiates the batchmode shutdown.