iOS calls that don't drop.
The debugging knowledge I wish I had earlier — free, no email required.
Every chapter is a specific bug I shipped a fix for in production. If you're building voice or video on iOS, this is the shortest path from “calls connect sometimes” to “calls survive cold starts, locked devices, Bluetooth handoff, and 3G.”
- 01Chapter
The cold-start silence
When PushKit wakes your app but the call connects mute.You get the VoIP push, you report to CallKit, the peer connection says connected — and the user hears nothing. The bug is in a 50-millisecond window between PushKit and AVAudioSession. Here's how to find it, and how to fix it so it stays fixed.
7 min readWebRTCAVAudioSessionPushKitCallKit - 02Chapter
The SDP offer/answer race
Two peers, one reconnect, zero chance your state machine survives.WebRTC's RTCPeerConnection is a tiny state machine with vicious edges. Under network loss and ICE restart, offer and answer can interleave and the connection stalls. The fix is one Swift actor — but you have to see the failure first.
6 min readWebRTCSDPSwift ActorsICE restart - 03Chapter
CallKit + FaceID: the 2-second audio gap
Locked devices eat the opening of every call. Here's why — and how to pre-warm the media path.The device is locked. VoIP push arrives. You call reportNewIncomingCall. The ring plays. The user Face-IDs in. They answer. And they hear nothing for 1-2 seconds. Classic. The fix decouples CallKit reporting from UI presentation.
5 min readCallKitPushKitFaceIDlifecycle - 04Chapter
Four signaling transports, one WebRTC engine
Why signaling — not WebRTC — is the hard part on iOS. And how I made four transports interchangeable.Everybody writes the WebRTCPeerConnection wrapper. Nobody tells you how to carry the SDP. Here are four transports I shipped side-by-side in one open-source demo: clipboard, step-by-step, Multipeer, and Local Network / Bonjour — all behind the same Codable envelope.
8 min readWebRTCMultipeerBonjoursignaling - 05Chapter
Ghost calls across devices
Picking up on one device, leaving the others ringing — a classic distributed-state bug.The user picks up on their iPhone. Their iPad keeps ringing. Then both devices answer and the server opens two media legs. Welcome to multi-device call sync — the kind of bug you only find in production. The fix: subscribers, not owners.
6 min readWebRTCWebSocketsdistributed state
Why I'm writing this.
Most WebRTC content online is either the spec, or a hello-world. The gap in the middle — the production-grade things nobody wrote down — is where I spent most of my decade. These chapters are the notes.
No email wall. No course. If one chapter saves you two days of debugging, forward it to someone who's stuck. If a company reading this needs to ship real voice or video on iOS and wants help, tell me what you're building.