I was able to narrow down the problem to network communication. During the compilation phase, the B4i bridge on the iPhone communicates with B4i on the PC without any problems. When the installation starts, the B4i bridge sometimes closes an existing TCP connection cleanly [FIN, ACK]. All subsequent connection attempts fail because new TCP [SYN] packets sent by B4i are immediately answered by the B4i bridge with TCP [RST] responses. This indicates that connection attempts are actively rejected at the TCP level, preventing a new session from being established. As a result, the client repeatedly sends [SYN] packets, leading to repeated connection attempts, application-level timeouts, and a general perception of extremely slow data transfer.
Could it be that the B4i Bridge temporarily switches to the background when the installation dialog is shown and therefore the connection is interrupted? If this is not already being done, would it be possible to start a background task via the iOS operating system when switching to the background, which would take over further processing for a limited period of time until the Bridge returns to the foreground?