Skip to main content
0 means success; anything other than 0 is an error. Every error code is structured as prefix + a 3-digit specific code (001–999). Once you can read the prefix, you can tell right away which layer and which platform the error comes from.

​
How to read an error code

There are three cases:

​
Platform types

The Swift SDK supports both iOS and macOS and automatically uses the 203 or 205 prefix depending on the platform it runs on.

​
Why you see error codes starting with 1xxxxx

This is expected, not a bug. SMeeting is built on SRTC. When an error occurs in the underlying audio and video layer, SMeeting passes SRTC’s original error code through to you as-is instead of wrapping it in its own code—so you can pinpoint which layer the problem is in. So seeing both 203002 and 103002 in the iOS conferencing SDK is not a contradiction: the former is error 002 of the meeting layer, and the latter is error 002 of the SRTC layer; the two are unrelated.
When troubleshooting, look at the first two digits first: if it starts with 2, look for meeting-layer causes (permissions, meeting state, member roles); if it starts with 1, look for audio and video layer causes (token, channel, network).

​
Full error code tables by platform

Web (Chinese) · Android · Windows (Chinese) · Swift · iOS (Chinese)
Don’t branch on the error message text—the text may change between versions, but error codes don’t.