1029: During a call,
AudioSessionCategory should be set to
AVAudioSessionCategoryPlayAndRecord, and the SDK monitors this value. If the
AudioSessionCategory is set to other values, this warning code is triggered and the SDK will forcefully set it back to
1052: Audio Device Module: The device is in the glitch state.
1042: Audio device module: The audio recording device is different from the audio playback device, which may cause echoes problem. Agora recommends using the same audio device to record and playback audio.
1025: Audio Device Module: call is interrupted by system events such as phone call or siri etc.
1040: Audio device module: An error occurs in the audio driver. Solutions:
1020: Audio Device Module: a playback device fails.
1032: Audio Device Module: the playback audio is too low.
1031: Audio Device Module: the recorded audio is too low.
1019: Audio Device Module: no valid audio data is collected.
1033: Audio Device Module: The recording device is busy.
1021: Audio Device Module: a recording device fails.
1014: Audio Device Module: a warning occurs in the playback device.
1016: Audio Device Module: a warning occurs in the recording device.
1051: Audio Device Module: Howling is detected.
1053: Audio processing module: A residual echo is detected, which may be caused by the belated scheduling of system threads or the signal overflow.
701: An error occurs in opening the audio mixing file.
16: Failed to initialize the video function, possibly caused by a lack of resources. The users cannot see the video while the voice communication is not affected.
8: The specified view is invalid. Specify a view when using the video call function.
105: The server rejects the request to look up the channel. The server cannot process this request or the request is illegal.
104: A timeout occurs when looking up the channel. When joining a channel, the SDK looks up the specified channel. The warning usually occurs when the network condition is too poor for the SDK to connect to the server.
103: No channel resources are available. Maybe because the server cannot allocate any channel resource.
121: The SDK fails to join a channel.
107: The server rejects the request to open the channel. The server cannot process this request or the request is illegal.
106: The server rejects the request to look up the channel. The server cannot process this request or the request is illegal.
122: Try connecting to another server.
20: The request is pending, usually due to some module not being ready, and the SDK postpones processing the request.
119: The client role is unauthorized.
118: A timeout occurs when setting the client role in the live broadcast profile.
1612: Super-resolution warning: The device does not support the super-resolution algorithm.
1610: Super-resolution warning: The origin resolution of the remote video is beyond the range where the super-resolution algorithm can be applied.
1611: Super-resolution warning: Another user is already using the super-resolution algorithm.
111: A timeout occurs when switching to the live video.
Generated using TypeDoc
Warning codes occur when the SDK encounters an error that may be recovered automatically. These are only notifications, and can generally be ignored. For example, when the SDK loses connection to the server, the SDK reports the
OpenChannelTimeout(106)warning and tries to reconnect automatically.