Validate the following:
- watchRTC.init() MUST be called before any call to RTCPeerConnection or those connections will not be captured.
- Are you using a CPaaS SDK or any other third-party WebRTC library? Make sure to include it AFTER you include AND call watchRTC.init()
- That said, do note that until a peer connection is actually opened, you won’t see any network traffic related to watchRTC.
Now that we covered the basics, follow these debugging steps.
Print SDK logs for debug perspective
To print SDK logs in your application, you must set a logger. This can be done by calling
watchRTC.setLoggerImpl(WatchRTCLoggerImpl()) function.
watchRTC.setLoggerImpl(WatchRTCLoggerImpl())Custom logs
You can use your custom logs implementation with the ILogger interface implementation.
ILogger is an interface for logging in WatchRTC SDK. Please implement this interface and pass the object reference in the watchRTC.setLoggerImpl(iLogger: ILogger) function.
watchRTC.setLoggerImpl(iLogger: ILogger)Common integration issues
- Calling watchRTC.init() after opening a peer connection.
- Calling watchRTC.init() after including a third-party WebRTC SDK.
- Setting the peerId and roomId only after opening a peer connection.
- Using the wrong API key.