Pipecat client iOS SmallWebRTC 1.1.1

[filipi87]

Pipecat client iOS SmallWebRTC 1.1.1:

• Trickle ice support
• Allowing startBotAndConnect to work with Pipecat cloud and Pipecat runner

[mattieruth]

i think this looks good except for the one rename and one question about validating the start bot return. i have to trust you on the ice candidate code.

[mattieruth]

Suggested change

	private func maybeLocalAudioTrack() {
	private func maybeCreateLocalAudioTrack() {

[filipi87]

I could swear I had renamed it like this. 😅 Nice catch.

[filipi87]

Done.

[mattieruth]

before we assume the startBotResult is bad because it doesn't match our built-in pipecat runner's return, should we add a check to make sure the startBotResult isn't already of type SmallWebRTCTransportConnectionParams?

[filipi87]

We already have that, right in the three lines above this code. 🙂

[mattieruth]

doh. i see that now. because of the name existingParams and my non-existent swift experience, i thought those lines were checking for if ConnectionParams had been provided prior to startBot (i.e. if there were existing params).

So that makes me now think: Do we consider THAT scenario? On web, you can provide connection options in the constructor. Is that possible on iOS? Could someone have provided the connection options ahead of time and used startBot simply to kick off the bot, not requiring any return data from the endpoint and then fail here?

[filipi87]

We only allow providing the connection options inside the connect method.

So, in this case, they would need to invoke startBot and then call connect right after.

I think it’s fine to use it that way, instead of also allowing the connection options to be passed to the constructor.