iOS Question Sending data to remote compiler

[davemorris]

Hi, Guys

Just started (today for the last 30minutes) to have some problems with the remote compiler.

B4i Version: 6.30
Parsing code. (0.19s)
Building folders structure. (0.26s)
Compiling code. (2.95s)
Compiling layouts code. (0.12s)
Compiling debugger engine code. (5.43s)
Building Xcode project (0.42s)
Sending data to remote compiler. Error
Communication error: Timeout

Timeout is set for 120 seconds, which in the past has been more than enough.

Is there something wrong (or is it my code)?

Kind regards
Dave

 

[Gijsen]

I have the same problem

 

[aeric]

 

[davemorris]

Hi

Have you actually tried today with a timeout of 300 seconds, does it work for you?

I did try 300 seconds on my project and one of Erel's tutorial examples (to test it was not my code) and it still timed out.

Dave

 

[Erel]

I'm checking this issue.
You should switch to the secondary builder when such problems happen. It is configured in the build server settings.

 

[aeric]

Hi

Have you actually tried today with a timeout of 300 seconds, does it work for you?

I did try 300 seconds on my project and one of Erel's tutorial examples (to test it was not my code) and it still timed out.

Dave

Yes, I try compile as Debug and as Release Build with no time out.

Spoiler

 

[davemorris]

Hi
Thanks Erel, using the secondary builder works (sorry, I was unaware it existed - obviously need to read through the manual again).

Question, do we only use the secondary builder if necessary and switch back the primary builder ASAP. Or is it ok to leave the IDE one and only switch to the other when it develops a problem.


Kind regards
Dave

 

[Erel]

The secondary builder is not really secondary. There are currently two builders and they are the same. Each user is assigned a default builder. The secondary builder option just switches to the second one.

There is no problem with keeping this option checked.