Windows:10
Builder:3.59
iOS: 16.2
% CocoaPods daemon still busy after 120 seconds. Aborting start. %
This error comes up sometimes in our build automation when trying to build using CLI. Is there a way to increase the timeout?
Thanks in advance
Windows:10
Builder:3.59
iOS: 16.2
% CocoaPods daemon still busy after 120 seconds. Aborting start. %
This error comes up sometimes in our build automation when trying to build using CLI. Is there a way to increase the timeout?
Thanks in advance
Hello
Yes, you can. This delay is hardcoded in the Toolchain\cocoapods\cocoapods.cmd file.
But instead of doing that, it might be preferable to investigate why the CocoaPods virtual machine takes so much time to start on your computer ? I personally find a 2 minutes startup excessive. What are the host computer’s specifications ?
If ram usage is not a problem, and you do frequent full rebuilds on the same machine, you can also prevent the VM from automatically shut down (in the same file).
I'm using contabo.com VPS with these specs
4 vCPU Cores
8 GB RAM
400 GB SSD
It doesn't happen often but sometimes it happens
On shared hosting, CPU power is rarely guaranteed. If the other VMs hosted on the same physical CPU are all busy, yours will get very little CPU time. In this case it makes sense to increase the timeout.
Moderators: Pierre-Marie Baty