Search Issue Tracker
Not Reproducible
Votes
0
Found in
2020.3
2020.3.8f1
Issue ID
1343843
Regression
No
[iOS] Batchmode abort "Timeout after 300 seconds" when building using Command Line Interface
Reproduction steps:
1. Download and unzip the project that the customer attached
2. On CLI execute command <Unity installation> -projectPath <Path of the project> -executeMethod BuildCommand.BuildIOSDevelopment -buildTarget ios -logFile <Log file location> -batchmode -quit -nographics --gameVersion 1.0 --buildNumber 80
3. Wait
Expected result: Build completes and control is given over to application that launched the command (terminal for example)
Actual result: Build suceeds (system notification appears) however control is not given back, after 5 minutes "Timeout after 300 seconds while waiting async operations to finish. executeMethod 'BuildCommand.BuildIOSDevelopment'" is thrown
Reproducible with: 2020.3.6f1
Not reproducible with: 2020.3.13f1
Could not test with: 2018.4.36f1, 2019.4.29f1, 2021.1.15f1, 2021.2.0b4, 2022.1.0a2 (package, namespace errors)
Note: the repro scenario is not consistent. The customer mentioned that the issue always reproduces when using a CI setup. I could not reliably test this to find out the exact fix version, but the customer mentioned that the issue no longer occurs in 2020.3.13f1 for them
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
- Windows Player exe contains unwanted properties, causing text "Unity Playback Engine" to appear in task bar when mousing over it
- Changes made by the Script in the UI Document are reset when performing an Undo operation after changing the GameObject with this Script
- Emissive materials are broken when loading Scene via SceneManager.LoadScene
- [URP] [Decals] ProxyLighting Decal shader doesn't work in Screen Space Technique
- "Pin in New Scene Dialog" option position migrates with "Inspector" window resizing
Resolution Note:
Does not reproduce in 2020.3.13f1
If you manage to reproduce the issue in newest versions of other streams or 2020.3.13f1 or higher, please submit a bug report with a scenario.