/** * Traces the iOS audio session diagnostics and the ADM engine state while a * StreamCall provider is mounted, and restarts a dead audio engine. * * WebRTC's iOS ADM can keep a failed engine start as "running", which leaves * the mic (or the playout) dead for the rest of the call. On every trigger * (join, mic enabled, CallKit activation, interruption end, app foreground, * route change, reconnect) the engine state is sampled, except during an * audio interruption. An unhealthy engine with an inactive audio session gets * one SDK re-activation (`reactivateAudioSession`); when iOS refuses it * (another app owns the audio) the tracer waits for the next interruption * end, session activation or app foreground, keeping its budget; any other * re-activation failure is re-checked on a budget of its own (same size and * spacing as the engine recovery below). Otherwise an unhealthy engine * is restarted with `AudioDeviceModule.recoverEngineIfNeeded`, at most * {@link MAX_EPISODE_ATTEMPTS} times per failure episode (re-checked * {@link ATTEMPT_INTERVAL_MS} after each failed attempt) and * {@link MAX_CALL_ATTEMPTS} times per call. When a whole episode fails, the * call is rejoined once (last resort, mic wanted and app in the foreground; * skipped when the rejoin would make the call leave). Either way the episode * ends there: the next trigger starts a new one (nothing is rescheduled). * Healthy samples are traced too (minimal payload) so the failure rate is * measurable. * * It also traces the ADM engine errors (the actual failure reasons), and an * `audio.session.timeout` when the SDK-owned audio session is still inactive * {@link SESSION_TIMEOUT_MS} after joining. */ export declare const AudioSessionDiagnosticsTracer: () => null; //# sourceMappingURL=AudioSessionDiagnosticsTracer.d.ts.map