Description: Can not run AI voice changer on this device. Cause: AI voice changer feature can not run on this device because of poor perforamance. Solutions: Do not use AI voice changer feature on this device.
Description: Failed to create AI voice changer. Cause: The instance exceeds the maximum limit. Solutions: Use an existing AI voice changer instance or destroy the previous instance.
Description: Initialize AI voie changer failed. Cause: Did not set user ID before initialize AI voice changer, or AI voice changer service expired. Solutions: Set user ID before initialize AI voice changer, or contact ZEGO technical support to deal with it.
Description: No AI voice changer resource files. Cause: AI voice changer resource files were not downloaded. Solutions: Please make sure AI voice changer resource files downloaded before use it.
Description: AI voice changer was not initialized. Cause: Did not initialize AI voice changer before use it. Solutions: Use AI voice changer after initialize it.
Description: The number of instances of the audio effect player created exceeds the maximum limit. Cause: The number of instances of the audio effect player created exceeds the maximum limit. Solutions: Please check if the number of instances of the audio effect player created exceeds the maximum limit, the maximum number of instances allowed to be created is 1.
Description: Load audio effect resource failed. Cause: Invalid audio effect resource file. Solutions: Check the file format is in the AudioEffectPlayer support file format list or not.
Description: No audio effect player instance. Cause: The audio effect player instance not created. Solutions: Create an audio effect player instance before using it(createAudioEffectPlayer).
Description: Play audio effect failed. Cause: Invalid audio effect resource file. Solutions: Check the file format is in the AudioEffectPlayer support file format list or not.
Description: Server access denied. Cause: 1.The APP has enabled the restriction of access from foreign IP addresses, and the current client is outside of the domain. Solutions: Please contact ZEGO technical support.
Description: The backend configuration of the server is incorrect. Cause: 1. The domain name configuration is incorrect; 2. The media network is abnormal; 3. The media network link is empty. Solutions: Please contact ZEGO technical support.
Description: This AppID has been removed from production. Solutions: Please check the status of the AppID on the ZEGO official website console or contact ZEGO technical support.
Description: The Input CDN auth param is too long. Cause: The length of auth parameter passed in when calling enablePublishDirectToCDN or startPlayingStream exceeds the limit. Solutions: Auth param length should be less than 1024 bytes.
Description: Incorrect CDN address. Cause: The set CDN URL is not a standard RTMP or FLV protocol. Solutions: Please check the supported protocol and format.
Description: The Input CDN URL is too long. Cause: The length of URL parameter passed in when calling enablePublishDirectToCDN or startPlayingStream exceeds the limit. Solutions: URL length should be less than 1024 bytes.
Description: The engine audio and video module has been activated, and this setting is not supported. Cause: Only supports setting before starting the audio and video module of the engine. Solutions: Please set it before calling startPreviewViewstartPublishingStreamstartPlayingStream to start the audio and video module.
Description: The room is logged in, this setting is not supported. Cause: Only supports setting before logging into the room. Solutions: Please set it before calling loginRoom or after calling logoutRoom. Note that if you log in to multiple rooms, you need to log out of all rooms before setting.
Description: The engine is not initialized and cannot call non-static functions. Cause: Engine not created. Solutions: Please call the createEngine function to create the engine first, and then call the current function.
Description: The audio and video module of the engine is not started and cannot support function realization. Cause: Audio and video modules with no engine started. Solutions: Please call startPreviewViewstartPublishingStreamstartPlayingStream to start the audio and video module first.
Description: setEventHandler has been called to set the handler, please do not set it repeatedly. Cause: Call setEventHandler repeatedly to set the handler. Solutions: If you need to repeat the settings, please call setEventHandler first to empty the previous handler.
Description: Illegal param. Cause: The parameter is empty, or the parameter is an illegal value. Solutions: Please check param when entered function to make sure it is correct.
Description: SDK internal null pointer error. Cause: The Android JVM environment is abnormal. Solutions: Please check whether the Android JVM environment is normal or contact ZEGO technical support.
Description: Failed to obtain SDK export function when loading SDK dynamic library. Cause: SDK dynamic library version does not match. Solutions: Please load the matching version of the SDK dynamic library.
Description: This call is not supported. Cause: ZEGOEXP_EXPLICIT macro is not enabled. Solutions: Please add the ZEGOEXP_EXPLICIT macro to the preprocessor.
Description: Not logged in to the room, unable to support function implementation. Cause: Not logged in to the room. Solutions: Please call loginRoom to log in to the room first, and use related functions during the online period after entering the room.
Description: The current SDK does not support this feature. Cause: The SDK version used does not include this feature. Solutions: Please contact ZEGO technical support.
Description: The input streamID contains invalid characters. Cause: The streamID parameter passed in when calling startPublishingStream or startPlayingStream contains invalid characters. Solutions: Check whether the streamID parameter passed in when calling the function is normal, only support numbers, English characters and '-', '_'.
Description: The input StreamID is null. Cause: The streamID parameter passed in when calling startPublishingStream or startPlayingStream is null or empty string. Solutions: Check whether the streamID parameter passed in when calling the function is normal.
Description: The input streamID is too long. Cause: The length of the streamID parameter passed in when calling startPublishingStream or startPlayingStream exceeds the limit. Solutions: The streamID should be less than 256 bytes.
Description: Call functions that are not supported on the current system/platform. Cause: For example, calling the function of setting the Android context environment on a non-Android system. Solutions: Check if the system environment matches.
Description: When login room or login scene, userID or user name is different. Cause: Login room, login scene use different user id or user name. Solutions: Use same user id and user name when login room, login scene.
Description: The command invalid. Cause: The command entered by the sendExtendedRequest function is empty. Solutions: Please check the command entered when calling the sendExtendedRequest function to make sure it is not empty.
Description: Copyright music init authentication failed. Cause: Appsign or token is not set. Solutions: When using token authentication, call loginRoom before calling initCopyrightedMusic or use appsign authentication.
Description: Request copyrighted server fail. Cause: The params entered make mistake or some network reasons. Solutions: Please check the params entered and retry.
Description: The number of times the resource is free in the room is exhausted. Cause: 1. The shared resources cannot be obtained again; 2. Shared resources have been obtained. Solutions: Please use the acquired resources, or use requestResource to share resources again.
Description: krcToken illegal. Cause: krcToken illegal. Solutions: Please check krcToken when entered by calling getKrcLyricByKrcToken to make sure it is correct.
Description: The krcToken invalid. Cause: The krcToken entered is empty. Solutions: Please check the krcToken entered when calling the function to make sure it is not empty.krcToken can be obtained by call requestResourcegetSharedResource
Description: Loading copyright music plugin failed. Cause: The program runtime path does not include the copyright music plugin dynamic library. Solutions: Please configure the copyright music plugin dynamic library dependency correctly.
Description: The copyright music module is not initialized. Cause: The initCopyrightedMusic method is not called to initialize the copyright module. Solutions: Please call the initCopyrightedMusic method first.
Description: No permissions of accompaniment, can only listen to songs, not sing. Cause: No permissions of accompaniment. Solutions: Please select another music.
Description: This resource is not shared in the room. Cause: No users in the room share this resource. Solutions: Please any one user in the room to call the requestresource function to request resources and share them.
Description: The copyright music module does not support this method. Cause: The copyright music module does not support this function under the current platform. Solutions: Contact ZEGO technical support to deal with it.
Description: The page parameter is invalid for multiple copyright searches. Cause: The page parameter must be 1 when multiple rights search is called for the first time. Solutions: Please pass in the correct page.
Description: The params invalid. Cause: The params entered by the sendExtendedRequest function is empty. Solutions: Please check the params entered when calling the sendExtendedRequest function to make sure it is not empty.
Description: The position invalid. Cause: The position entered by the fuction seek is invalid. Solutions: Please check the position entered when calling the function seek to make sure it is in 0 ~ song duration.
Description: The copyrighted resource has expired. Cause: The copyrighted resource has expired. Solutions: Please request the copyrighted resource again.
Description: The resource_id invalid. Cause: The resource_id entered is empty. Solutions: Please check the resource_id entered when calling the function to make sure it is not empty.resource_id can be obtained by call requestResourcegetSharedResourcegetMusicByToken
Description: The resource_id unauthorized. Cause: The resource ID is not obtained through requestResourcegetSharedResource function. Solutions: Please call the requestResourcegetSharedResource function to get valid resource ID.
Description: The room ID is not logged in. Cause: Room ID input error. Solutions: If the copyright is not used in a multi room scenario, there is no need to pass in the roomID, otherwise please pass in the correct logged in room ID.
Description: Share token illegal. Cause: Share token illegal. Solutions: Please check songToken when entered by calling getMusicByToken to make sure it is correct.
Description: The share_token invalid. Cause: The share_token entered is empty. Solutions: Please check the share_token entered when calling the function to make sure it is not empty.share_token can be obtained by call requestResource
Description: The song_id invalid. Cause: The song_id entered is empty. Solutions: Please check the song_id entered when calling the function to make sure it is not empty.
Description: This vendor does not support this song ID. Cause: This song ID does not exist in the copyright music library. Solutions: Please pass in the correct song ID.
Description: The start_position invalid. Cause: The start_position entered by the fuction loadCopyrightedMusicResourceWithPosition is invalid. Solutions: Please check the start_position entered when calling the function loadCopyrightedMusicResourceWithPosition to make sure it is in 0 ~ song duration.
Description: The vendor is unavailable. Cause: The corresponding copyright party has not been activated. Solutions: Please pass in the correct vendor ID.
Description: The volume invalid.. Cause: The Volume entered by the fuction setPlayVolume is invalid. Solutions: Please check the Volume entered when calling the function setPlayVolume to make sure it is in 0 ~ 200.
Description: The sample rate parameter is illegal. Cause: Capture and render mix results recording does not support 8000, 22050, 24000 sample rates. Solutions: Please confirm whether the sample rate parameter value allowed by the interface is legal.
Description: The custom audio capture feature is not enabled. Cause: The custom audio capture feature is not enabled. Solutions: Please make sure that the custom audio IO module is enabled for the specified stream publishing channel.
Description: Failed to enable/disable custom audio IO. Cause: Failed to enable/disable custom audio IO. Solutions: Please make sure to enable/disable it before the engine is started (i.e., before calling startPreview, startPublishingStream or startPlayingStream).
Description: The custom audio rendering feature is not enabled. Cause: The custom audio rendering feature is not enabled. Solutions: Please make sure that the custom audio IO module is enabled.
Description: The custom video capturer is not created. Cause: Create custom video capturer before onStart callback received. Solutions: Please create custom video capturer after received onStart callback.
Description: Failed to enable/disable custom video capture/rendering. Cause: Not enable/disable custom video capture/rendering before engine is started. Solutions: Please make sure to enable/disable custom video capture/rendering before engine is started, i.e., before calling (startPreview), (startPublishingStream), (startPlayingStream), (createMediaPlayer) or (createAudioEffectPlayer).
Description: The custom video capture module is not enabled. Cause: Custom video capture module is not enabled in initialization configurations. Solutions: Please contact ZEGO technical support, make sure custom video capture module is enabled in initialization configurations.
Description: The custom video process module is not enabled. Cause: The custom video process module is not enabled. Solutions: Call enableCustomVideoProcessing to enable a custom video capturermodule.
Description: Custom video rendering does not support the currently set video buffer type. Cause: The buffer_type in the config parameter of enableCustomVideoRender only supports raw_data, cv_pixel_buffer, encoded_data. For enableCustomVideoProcessing, only raw_data is supported on Windows platform, only cv_pixel_buffer is supported on Apple devices, and gl_texture_2d and surface_texture are supported on Android platform. Solutions: Select the correct video buffer type.
Description: The currently configured custom video capture format does not support this API. Cause: The currently configured custom video capture format does not support this API. Solutions: Please contact ZEGO technical support.
Description: The custom video capturer is not created. Cause: Internal video-related modules are not created. Solutions: Please call startPreview or startPublishingStream first.
Description: The set audio spectrum monitoring interval is out of range. Cause: The set audio spectrum monitoring interval is less than 10 milliseconds. Solutions: Reset audio spectrum monitoring interval which is not less than 10 milliseconds.
Description: Generic device error. Cause: Device dose not work normally. Solutions: Use the system's video or audio recording application to check whether the device can work normally. If the device is normal, please contact ZEGO technical support.
Description: The device is occupied. Cause: The device is occupied by other programs. Solutions: Please use the system's video or audio recording application to check whether the device is working properly and make sure that the device is not occupied by other applications.
Description: The device ID does not exist. Cause: The device ID is spelled incorrectly, or the corresponding device is unplugged. Solutions: Please use the SDK interface to obtain the device ID, and check whether the device is properly connected.
Description: No permission to access the device. Cause: Did not apply for or obtain the permission to use the corresponding device. Solutions: Please check whether the application has correctly applied for the camera or microphone permission, and whether the user has granted the corresponding permission.
Description: The device is unplugged. Cause: The device is unplugged or not properly connected. Solutions: Check the device wiring and reconnect the device.
Description: The frame rate of the capture device is 0. Cause: Device error, or device does not have permission. Solutions: Please use the system's video or audio recording application to check whether the device can work normally. Please check whether the application has correctly applied for the camera or microphone permission, and whether the user has granted the corresponding permission. If the device is normal and the application has obtained the corresponding device permissions, please contact ZEGO technical support.
Description: Failed to set the camera exposure compensation. Cause: The set camera exposure compensation value is out of range. Solutions: Set the camera exposure compensation range between -1,1.
Description: The device list cannot be empty when trying to release devices. Cause: The device list has been released or has not been initialized. Solutions: Ignore it.
Description: The set sound level monitoring interval is out of range. Cause: The set sound level monitoring interval is less than 100 milliseconds, or greater than 3000 milliseconds. Solutions: Reset the effective sound level monitoring interval, the effective sound level monitoring interval is 100, 3000, in milliseconds.
Description: Failed to set the camera zoom. Cause: The set camera zoom factor is out of range. Solutions: The set camera zoom factor cannot exceed the maximum range obtained, the maximum range can be obtained through getCameraMaxZoomFactor.
Description: Authentication failed. Cause: Incorrect AppID; using AppID in wrong environment. Solutions: Please check AppID is correct or not on ZEGO manage console, or check whether the environment configured by AppID is consistent with the environment set by SDK.
Description: The experimental API json parameter parsing failed. Cause: Invalid json format; wrong function name or parameter. Solutions: Please check json format is valid or not; check function name or parameter is correct or not, contact ZEGO technical support for specific function name and parameters.
Description: No write permission to the log file. Cause: App has no write permission to log file folder. Solutions: Please check has grant write permission to App or not; check log folder is protected or not.
Description: The input real-time sequential data is too long. Cause: The length of the input data is greater than 4096 bytes. Solution: Check the length of the input data, consider splitting the large data packet into multiple small data and sending it multiple times.
Description: The room where the message is sent is different from the room currently logged in. Cause: The room where the message is sent is different from the room currently logged in. Solutions: Send a message to the current logged-in room ID.
Description: Failed to send message. Cause: The message input length exceeds the limit. Solutions: Check the input content length or contact ZEGO technical support to expand the message content length.
Description: The real-time sequential data manager instance creation failed. Cause: A manager instance with this room ID has already been created. Solution: A maximum of 1 instance can be created for each room ID. If you need to create multiple instances, please use other room IDs.
Description: No publish channel available for broadcasting. Cause: The developer has used all publish channels. Solution: Do not use all the publish channels, check if there are any streams that can stop publsihing, or contact ZEGO technical support to increase the available publish channels.
Description: The stream ID to start broadcasting is not available. Cause: The stream ID has been used in this device for RTC business (e.g. startPublishingStream / startPlayingStream). Solution: Please use another stream ID for broadcasting.
Description: The stream to stop broadcasting does not exist. Cause: The stream ID set stopBroadcasting function is not in broadcasting. Solution: Check if the stream ID is correct, or if the stream ID is not in broadcasting.
Description: The specified real-time sequential data manager instance could not be found. Cause: This manager instance has not been created yet. Solution: Please call the createRealTimeSequentialDataManager function to create a manager instance first.
Description: The stream to stop subscribing does not exist. Cause: The stream ID set stopSubscribing function is not in subscribing. Solution: Check if the stream ID is correct, or if the stream ID is not in subscribing.
Description: Failed to send real-time sequential data. Cause: The broadcast has not started yet, or the broadcast has encountered network problems. Solution: Check whether startBroadcasting has been called to start broadcasting, or check whether the network is normal.
Description: Repeat broadcast. Cause: The developer repeatedly calls the startBroadcasting function. Solution: Please check the business logic to avoid repeating the broadcast for the stream which is broadcasting.
Description: Repeat broadcast. Cause: The developer repeatedly calls the startBroadcasting function. Solution: Please check the business logic to avoid repeating the subscribe for the stream which is subscribing.
Description: Failed to send custom signaling. Cause: The entered user ID is too long. Solutions: Please enter the correct user ID, the maximum user ID cannot exceed 64 bytes.
Description: The number of instances of the media data publisher created exceeds the maximum limit. Cause: The number of instances of the media data publisher created exceeds the maximum limit. Solutions: Please check if the number of instances of the media data publisher created exceeds the maximum limit, the maximum number of instances allowed to be created is 1.
Description: File decoding exception. Cause: Invalid media file format. Solutions: Please check the file is a valid media file or not; check the file format is in the MediaPlayer support file format list or not.
Description: The MediaDataPublisher instance is not created. Cause: The MediaDataPublisher instance is not created. Solutions: Call createMediaDataPublisher to create a media pusher instance.
Description: Timestamp error. Cause: the later frame timestamp is smaller than the previous frame timestamp. Solutions: Please provide the media file, and contact ZEGO technical support.
Description: The MediaPlayer failed to load the file. Cause: There was an error during file resolution. Solutions: Try again or contact ZEGO technical support.
Description: The number of MediaPlayer instances exceeds the maximum number allowed. Cause: The number of MediaPlayer instances exceeds the maximum number allowed. Up to 4 instances can be created. Solutions: Media players can create up to 4 instances, and make sure that the number of media player instances is not exceeded the maximum limit.
Description: The MediaPlayer failed to load the file. Cause: The file decoding failed. Solutions: Check that the media file is corrupted or contact ZEGO technical support.
Description: The copyrighted music resource file has expired. Cause: The resource file has expired. Solutions: Please request song or accompaniment again.
Description: The MediaPlayer failed to load the file. Cause: File formats are not supported. Solutions: Files in this format are not supported, please use files in the supporting format.
Description: The MediaPlayer failed to load the file. Cause: No supported audio/video stream exists. Solutions: Check that the media file data is empty.
Description: The specified media file path is too long. Cause: The specified media file path is too long. The maximum length should be less than 1024 bytes. Solutions: Please specify media file path less than 1024 bytes.
Description: Failed to cache network resource file. Cause: During playback, seekTo operation will cause cache failure, and network reasons or incomplete playback caused by active stop will also cause cache failure. Solutions: Check whether there is a seekTo operation, whether the playback failed due to network reasons, or whether the playback stopped actively.
Description: The MediaPlayer failed to play the media. Cause: The resource file is not loaded. Solutions: The media player loads the media resource loadResource before starting.
Description: The MediaPlayer failed to play the media. Cause: The resource file is not loaded. Solutions: Create a media player instance before using media players createMediaPlayer.
Description: the passed parameter is not in the valid value range. Cause: error setting parameters. Solutions: Review the interface comment and pass in a value within the legal range.
Description: The MediaPlayer is configured with a video data format not supported by the platform. Cause: The MediaPlayer is configured with a video data format not supported by the platform (e.g., CVPixelBuffer on iOS does not support NV21). Solutions: Check the data format setVideoHandler supported by the current media player platform and set the correct data format.
Description: The copyrighted music resource has expired. Cause: The copyrighted music resource has expired. Solutions: Please request the copyrighted music resource again.
Description: The copyrighted music resource ID is too long. Cause: The copyrighted music resource ID is too long. The maximum length should be less than 512 bytes. Solutions: Please copyrighted music resource ID less than 1024 bytes.
Description: The MediaPlayer failed to seek. Cause: The file hasn't been loaded yet. Solutions: The media player loads the media resource loadResource before seeking seekTo.
Description: The media player failed to specify the audio track index. Cause: The audio track index not exist. Solutions: Check file audio track index call getAudioTrackCount can get.
Description: Media player setting sound change parameter invalid. Cause: Error setting parameters. Solutions: Checking setting parameters control during -12.0 to 12.0
Description: takeSnapshot screenshot failed Cause: The video is not playing or 'setPlayerCanvas' is not called to display the video to the control. Solutions: Check whether the video plays normally(check onPlayStart callback) and the screen is displayed normally.
Description: The mixed-flow advanced configuration is too long. Cause: The length of the mixed stream advanced configuration parameter exceeds the limit. Solutions: Please make sure that the advanced configuration length does not exceed 512 bytes.
Description: The video configuration of the stream mixing task is invalid. Cause: 1. An unsupported audio codec format is used. 2. The audio bit rate exceeds 192 kbps. Solutions: Please check the audio configuration of the stream mixing task.
Description: Failed to start mixed stream. Cause: The URL of the background image entered is illegal. Solutions: The URL of the background image must start with preset-id:// and end with .jpg or .png.
Description: The mixed stream background image url is too long. Cause: The length of the mixed stream background url parameter exceeds the limit. Solution: Please make sure the background image url length does not exceed 1024 bytes.
Description: Failed to start mixed stream. Cause: The maximum number of focus voice input streams is exceeded. Solutions: Support up to 4 input streams to set the focus voice.
Description: The number of input streams exceeds the maximum number allowed. Cause: Supports up to 9 input streams, and may pass more than 9 input streams. Solutions: Please check the input stream configuration of the mixing task.
Description: Failed to mix stream input image. Cause: The image format of the mixed stream input parameter is incorrect. Solution: Use JPG and PNG formats. There are 2 ways to use it: 1. URI: Provide the picture to ZEGO technical support for configuration. After the configuration is complete, the picture URI will be provided, for example: preset-id://xxx.jpg. 2. URL: Only HTTP protocol is supported.
Description: Failed to mux input image. Cause: The image size of the mixed stream input parameter exceeds the limit. Solution: Image size is limited to 1M.
Description: The link to the muxed input image is too long. Cause: The length of the image link of the mixed stream input parameter exceeds the limit. Solution: Please make sure that the length of the input image link does not exceed 1024 bytes.
Description: Mixed input text watermark is too long. Cause: The length of the text watermark of the mixed stream input parameter exceeds the limit. Solutions: Please make sure the input text watermark length does not exceed 512 bytes.
Description: The input stream list of the stream mixing task is empty. Cause: The input stream list of the stream mixing task is empty. Solutions: Please check the input stream list of the mixing task.
Description: Failed to start mixed stream. Cause: The mixed stream input parameter is wrong, it may be that the layout of the input stream exceeds the canvas range. Solutions: Please enter the correct mixed stream parameters. ZegoMixerTask
Description: Failed to start mixed stream. Cause: The input stream does not exist. Solutions: Please make sure that the stream corresponding to the entered streamID is being pushed.
Description: Illegal parameters exist in mixing task configuration. Cause: 1. The mixing task ID is empty; 2. The mixing room ID is empty; 3. The mixing custom data length exceeds 1000 bytes; 4. The mixing output target stream is empty. Solutions: Please check the configuration parameters of the mixing task.
Description: Does not support the use of stream mixing service. Cause: No stream mixing service configured. Solutions: Please open the service on the console or contact ZEGO business staff.
Description: The output stream list of the stream mixing task is empty. Cause: The output stream list of the stream mixing task is empty. Solutions: Please check the output stream list of the mixing task.
Description: Illegal format of mixed stream output target parameter. Cause: When the target of the mixed stream output target is streamID, an illegal character is passed in. Solutions: Please check whether the target of the mixed stream output target is of streamID type, if so, target only support numbers, English characters and '-', '_'.
Description: Mixed stream output target is too long. Cause: The length of the target parameter of the mixed stream output exceeds the limit. Solutions: Please make sure that the output destination length does not exceed 1024 bytes.
Description: Starts stream mixing tasks too frequently. Cause: Requests are too frequent, exceeding the qps limit of the service. Solutions: Please ensure that the qps of the mixing request is less than 100.
Description: Failed to start the stream mixing task. Cause: Requests are too frequent, exceeding the qps limit of the service. Solutions: Please ensure that the qps of the mixing request is less than 100.
Description: Stop stream mixing tasks too frequently. Cause: Requests are too frequent, exceeding the qps limit of the service. Solutions: Please ensure that the qps of the stop mixing request is less than 100.
Description: Invalid mixed flow task ID. Cause: Illegal characters in the stream mixing task ID. Solutions: Stream mixing task ID only supports numbers, English characters and'~','!','@','$','%','^','&','*','(',')', '_','+','=','-','`',';',''',',','.','<','>','/','', please enter the stream mixing task ID in the correct format.
Description: The mixing task ID is null. Cause: The mixing task ID input when starting mixing task is empty. Solutions: Please enter the correct mixing task ID.
Description: The stream mixing task ID is too long. Cause: The stream mixing task ID is greater than 256 bytes. Solutions: Please enter a mixing task ID less than 256 bytes.
Description: Failed to start mixed stream. Cause: The user-defined data is too long. Solutions: The maximum length of the custom input should not exceed 1000 bytes.
Description: The video configuration of the stream mixing task is invalid. Cause: The video configuration of the stream mixing task is invalid. Solutions: Please check the video configuration of the stream mixing task.
Description: Failed to start mixed stream. Cause: The input image watermark is empty. Solutions: Please enter the correct watermark parameters ZegoWatermark.
Description: Failed to start mixed stream. Cause: The input image watermark parameter is wrong, it may be that the layout exceeds the canvas range. Solutions: Please enter the correct watermark parameters ZegoWatermark.
Description: The mixed stream watermark path is too long. Cause: The length of the mixed stream watermark path parameter exceeds the limit. Solution: Please make sure the watermark path length does not exceed 512 bytes.
Description: Failed to start mixed stream. Cause: The input watermark URL is illegal. Solutions: The watermark URL must start with preset-id:// and end with .jpg or .png.
Description: Stream playing error. Caution: The number of streams the user attempted to play simultaneously exceeds the maximum number allowed. Solutions: Currently, up to 12 steams can be played at the same time. Please contact ZEGO technical support to increase the capacity if necessary.
Description: The play stream decryption key is invalid, the key length only supports 16/24/32 bytes. Cause: The input key length is not 16/24/32 bytes. Solutions: Adjust the input key length to 16/24/32 bytes.
Description: Play stream authentication is incorrect. Caution: The Token error or timeout required to playing stream across APP. Solutions: Playing the stream to pass the correct Token, or update the Token in time.
Description: Calling the wrong function after enabling the multi-room function causes playing stream fail. Cause: Called the playing stream function that only works for joining a single room mode. Solutions: Please use the function of the same name with ZegoPlayerConfig and specify the room ID to play the stream.
Description: In the multi-room mode, the roomID parameter of the play stream cannot be empty. Cause: The roomID parameter of the pull stream is empty. Solutions: Please enter the correct roomID.
Description: Failed to play the stream. Caution: Publishing of this stream is prohibited by backend configuration. Solutions: Please contact ZEGO technical support to solve the problem.
Description: An internal system exception causes a failure to pull the stream. Cause: SDK internal error. Solutions: Please contact ZEGO technical support.
Description: When using the SDK to play the latency of live streaming, this error code will be returned if you have not subscribed to the low latency live streaming service. Cause: Low-latency live broadcast service is not activated. Solutions: Please contact ZEGO technical support staff to open the low-latency live broadcast service.
Description: Stream playing failed. Caution: Possibly due to no data in the stream. Solutions: Check to see if the publish-stream is working or try to play stream again, and if the problem is still not resolved, please contact ZEGO technical support to solve the problem.
Description: Stream playing failed. Caution: The stream does not exist. Solutions: Please check whether the remote end publish is indeed successful, or whether the publish and play environment are inconsistent.
Description: The stream was not played. Caution: The stream was not played. Solutions: Please confirm that the stream has been played through the onPlayerStateUpdate or onUserStreamStateUpdate callback.
Description: This device does not support super resolution. Caution: The device configured on the server does not support super resolution, or the configuration on the server failed to pull. Solutions: replace the device and try again or contact ZEGO technical support.
Description: The performance of super resolution device is not enough. Caution: The performance of device is not enough. Solutions: Please replace the device.
Description: The number of super resolution streams exceeds the limit. Caution: The number of super resolution streams exceeds the limit. Solutions: Currently, super resolution support up to 1 playing steam at the same time.
Description: The number of super resolution streams exceeds the limit. Caution: The number of super resolution streams exceeds the limit. Solutions: contact ZEGO technical support.
Description: Failed to capture the screenshot of the streaming screen, please check whether the stream to be captured is normal. Cause: The stream is not pulled. Solutions: Check whether it starts to play the stream, and whether there is an abnormality in the process of playing the stream.
Description: Unsupported video decoder. Caution: There is no selected video decoder in the current SDK. Solutions: Please contact ZEGO technical support.
Description: Failed to set the beauty configuration. Cause: The incoming beauty parameters are incorrect. Solutions: Please check the passed in ZegoBeautifyOption type parameter.
Description: Failed to turn on or turn off the electronic sound effect. Cause: the initial pitch parameter tonal of the electronic tone is invalid. Solutions: The normal range of the starting pitch parameter of the electronic tone is 0 ~ 11.
Description: Failed to turn on or turn off the beauty effect. Cause: The beauty environment is not activated. Solutions: Please call startEffectsEnv to start the beauty environment first.
Description: Failed to open or close the beauty environment. Cause: The beauty environment was not turned on or off before the engine started. Solutions: Please make sure to turn on or turn off the beauty environment before the engine starts, for example: before calling (startPreview), (startPublishingStream), (startPlayingStream), (createMediaPlayer) or (createAudioEffectPlayer).
Description: Failed to enable speech enhancement. Cause: speech enhancement level parameter is invalid. Solutions: speech enhancement level ranges from 0 to 10. Use the correct parameter value.
Description: Effects Beauty does not support the currently set video data type. Cause: enableCustomVideoProcessing interface, Windows platform only supports raw_data, Apple device only supports cv_pixel_buffer, Android platform supports gl_texture_2d. Solutions: select the correct video data type.
Description: Failed to set the reverberation parameters. Cause: the reverberation damping parameter is invalid. Solutions: The normal range of the reverberation damping parameter is 0.0 ~ 2.0
Description: Failed to set the reverberation parameters. Cause: The dry_wet_ratio parameter of the reverberation is invalid. Solutions: The normal range of the dry_wet_ratio parameter of reverberation is greater than 0.0
Description: Failed to set the reverberation parameters. Cause: The reverberance parameter is invalid. Solutions: The normal range of the reverberance parameter is 0.0 ~ 0.5
Description: Failed to set the reverberation parameters. Cause: the reverberation room size parameter is invalid. Solutions: The normal range of the reverberation room size parameter is 0.0 ~ 1.0
Description: Failed to set beauty parameters. Cause: The beauty environment is not activated. Solutions: Please call startEffectsEnv to start the beauty environment first.
Description: Failed to start virtual stereo. Cause: The virtual stereo angle parameter is invalid. Solutions: The normal range of angle parameter is -1 ~ 360.
Description: Failed to set the voice changing parameters. Cause: The param setting of the voice changing parameter is invalid. Solutions: The normal range of parameter param is -12.0 ~ 12.0
Description: Failed to send audio side info. Cause: The input data exceeds the length limit. Solutions: The length of the sent audio side data should be less than 1024 bytes.
Description: Publishing failed due to wrong bitrate setting. Cause: The set video bitrate, audio bitrate, or minimum video bitrate threshold for traffic control exceeds the upper limit. Solutions: Please check if the bitrate value is in the correct unit (kbps).Adjust the bitrate setting.
Description: The specified path for displaying static images when the camera is turned off is incorrect. Caution: The path may be misspelled or there may be no read permission. Solutions: Please check if the designated image path is correct and if there is read permission.
Description: The publish stream encryption key is invalid. Caution: The set encryption key length is not supported. Solutions: The Publish-stream encryption key length to be 16/24/32 bytes.
Description: Failed to publish the stream. The publish channel is already publishing streams. Cause: The publish channel is already publishing streams. Solutions: Please check the business logic to avoid repeating the publish for publish channel which is publishing.
Description: Push-pull flow authentication is incorrect. Caution: An appSign error was passed when creating the engine, or a Token error or timeout was passed when logging into the room. Solutions: Pass the correct Token upon login, or invoke renewToken when recive onRoomTokenWillExpire callback.
Description: Streaming failed, H.265 encoding is not supported. Cause: The hardware device does not support H.265 encoding, or the SDK does not include H.265 encoding module. Solutions: Contact ZEGO technical support to confirm whether the SDK contains the H.265 encoding module, if the hardware device does not support it, it is recommended to upgrade the hardware.
Description:Stream publishing is temporarily interrupted and is retrying. Cause: The network fluctuates or the network signal is bad. Solutions: Please wait or check whether the network is normal.
Description: StartPlayingStream failed. Caution: In multi-room mode, the publish-stream function is called incorrectly. Solutions: In multi-room mode, A publish-stream function with the parameter 'ZegoPublisherConfig' needs to be called.
Description: StartPlayingStream failed. Caution: In multi-room mode, the publish-stream function is called incorrectly. Solutions: In multi-room mode, A publish-stream function parameter 'roomID' cannot be empty.
Description: Failed to publish the stream. The same stream already exists in the room. Cause: The same stream already exists in the room. Solutions: Replace with a new stream ID. Adjust the stream ID generation strategy to ensure uniqueness.
Description: Stream publish retry has exceeds the maximum retry time. Cause: The the network signal is bad, and the maximum retry time is exceeded. Solutions: Check the network status or switch to another network.
Description: Failed to publish the stream. Publishing of this stream is prohibited by backend configuration. Cause: Publishing of this stream is prohibited by backend configuration. Solutions: Contact ZEGO technical support to deal with it.
Description: Stream publishing failed due to system internal exceptions. Caution: Stream publishing failed due to system internal exceptions. Solutions: Please contact ZEGO technical support to solve the problem.
Description: This device does not support object segmentation. Caution: The device is not supported, or the object segmentation of multiple channels is enabled. Solutions: Please change the device or only open the object segmentation of one channel.
Description: Object segmentation background loading error. Caution: The background video or image path is incorrect, or the content is incorrect.. Solutions: Please set the correct background image or video.
Description: Object segmentation unauthorized. Caution: The appid is not configured with object segmentation. Solutions: Please contact ZEGO technical support to configure the object segmentation function.
Description: Object segmentation parameter error. Caution: Object segmentation is set to green screen type, background blur is not allowed. Solutions: Please use the correct parameters to enable object segmentation.
Description: The performance of object segmentation device is not enough. Caution: The performance of device is not enough. Solutions: Please replace the device.
Description: Publishing failed due to no data in the stream. Cause: No data in the stream. Solutions: Check whether the video, audio capture module is working properly.
Description: Failed to publish the stream. The connection to the RTMP server is interrupted. Cause: The publish address is wrong, or the network signal is bad. Solutions: Please check whether there is any problem with the network connection or the stream publishing URL.
Description: Failed to send SEI. Cause: The input data exceeds the length limit. Solutions: The length of the sent SEI data should be less than 4096 bytes.
Description: Failed to take a screenshot of the publis stream screen. Cause: The preview is stopped and the push is abnormal. Solutions: Turn on preview or re-publish.
Description: The property param of the traffic control is set incorrectly. Cause: The property param of the traffic control is less than 0 or exceeds all combinations. Solutions: Check the settings of the property param of the traffic control.
Description: Unsupported video encoder. Caution: There is no selected video encoder in the current SDK. Solutions: Please contact ZEGO technical support.
Description: Incorrect watermark layout. Caution: The layout area exceed the encoding resolution. Solutions: Make sure the layout area cannot exceed the encoding resolution and call current interface.
Description: Failed to set publish watermark. Cause: The incoming watermark path was entered incorrectly or the image format is not supported. Solutions: Incoming the correct watermark path, only jpg and png image formats are supported.
Description: Failed to set publish watermark. Cause: The incoming watermark path exceeds the byte size limit. Solutions: The incoming watermark path should be less than 512 bytes.
Description: Failed to set the team ID. Cause: The input user ID contains invalid characters. Solutions: User ID can only contains numbers, English characters and '~', '!', '@', '#', '$', '%', '^', '&', '*', '(', ')', '_', '+', '=', '-', '`', ';', ',', '.', '<', '>', '/', ''.
Description: Calling function failed. Cause: Illegal parameter or SDK does not contain RangeScene module. Solutions: Please confirm whether the SDK contains the RangeScene module and check the parameters.
Description: The number of RangeScene instances exceeds the maximum number allowed. Cause: The number of RangeScene instances exceeds the maximum number allowed. Up to 1 instances can be created. Solutions: RangeScene can create up to 1 instances, and make sure that the number of RangeScene instances is not exceeded the maximum limit.
Description: The item binding user exceeds the maximum limit. Cause: The item binding user exceeds the maximum limit. Solutions: The item binding user exceeds the maximum limit. Please try again later.
Description: The binding capacity of the item exceeds the maximum limit. Cause: The binding capacity of the item exceeds the maximum limit. Solutions: Please use a capacity that does not exceed the maximum binding capacity to create an item.
Description: Scene connection is temporarily interrupted. Cause: Possibly due to network problems. Solutions: Please wait or check whether the network is normal.
Description: The RangeScene instance not created. Cause: The RangeScene instance not created. Solutions: Create a RangeScene instance before using RangeScene createRangeScene.
Description: Use not support feature. Cause: Use the status synchronization interface when the status synchronization function is not enabled. Solutions: To use the status synchronization interface, please enable the status synchronization function.
Description: Scene login retry has exceeded the maximum retry time. Cause: Possibly due to network problems. Solutions: Please check whether the network is working or switch the network environment.
Description: The number of joined RangeScene teams exceeds the maximum number allowed. Cause: The number of joined RangeScene teams exceeds the maximum number allowed. Up to 5 are allowed by default. Solutions: RangeScene teams can joined are up to 5, and make sure that the number of RangeScene teams joned is not exceeded the maximum limit.
Description: Token verification failed. Cause: The parameters passed in during token generation are inconsistent with the SDK. Solutions: Please use the correct token regenerated.
Description: The user has bound the item to the maximum limit. Cause: The user has bound the item to the maximum limit. Solutions: Please unbind some items that do not need to be operated temporarily.
Description: Generic recording API error. Cause: Invalid input parameter. Solutions: Please check the record file path parameter or the record file format parameter is valid or not.
Description: The specified recorded file path is too long. Cause: The specified recorded file path is too long. The maximum length should be less than 1024 bytes. Solutions: Please specify recorded file path less than 1024 bytes.
Description: Open file failed. Cause: Invalid file path or no permissions to read/write file. Solutions: Please specify a valid file path and has proper permissions to read/write.
Description: The interface is called more frequently than the upper limit. Cause: This application calls this interface too often. Solutions: Please control the frequency of calls to this interface. Please refer to https://docs.zegocloud.com/article/7612 for details.
Description: Room signalling type interfaces are called more frequently than the upper limit. Cause: This application calls the room signalling type interface too often. (e.g., sendCustomCommandsendBroadcastMessage) Solutions: Please control the frequency of application calls to the room signalling type interface. Please refer to https://docs.zegocloud.com/article/7612 for details.
Description: Room connection is temporarily interrupted and is retrying. Cause: Possibly due to network problems. Solutions: Please wait or check whether the network is normal.
Description: The number of rooms the user attempted to log into simultaneously exceeds the maximum number allowed. Currently, a user can only be logged in to one main room. Cause: In single-room mode, log in to multiple main rooms at the same time (including repeated calls to log in to the same room A without exiting room A). Solutions: Please check is login multiple rooms simultaneously or not under single room mode.
Description: Room connection disconnected. Cause: Possibly due to network problems. Solutions: Please check whether the network is working or switch the network environment.
Description: Login failed, possibly due to network problems. Cause: The current network is abnormal. Solutions: It is recommended to switch the network to try.
Description: The number of users logging into the room exceeds the maximum number of concurrent users configured for the room. (In the test environment, the default maximum number of users in the room is 50). Cause: too much user in room. Solutions: contact ZEGO technical support.
Description: in test environment The total number of rooms logged in at the same time exceeds the limit. (In the test environment, the maximum number of concurrent rooms is 10). Cause: Too many rooms logged in at the same time. Solutions: logout some room, login room.
Description: Login timed out, possibly due to network problems. Cause: The current network delay is large. Solutions: It is recommended to switch the network to try.
Description: Room login failed due to internal system exceptions. Cause: Unknown internal error. Solutions: Contact ZEGO technical support to deal with it.
Description: The user was kicked out of the room. Cause: Possibly because the same user ID is logged in on another device. Solutions: Use a unique user ID.
Description: The business server has sent a signal to kick the user out of the room. Cause: The business server has sent a signal to kick the user out of the room. Solutions: Contact the business server for processing.
Description: This method has been deprecated after version 2.9.0. Cause: This method has been deprecated after version 2.9.0. Solutions: Please set setRoomMode to select multi-room mode before the engine started, and then call loginRoom to use multi-room.
Description: set multi room mode, userID or user name is different. Cause: set multi room mode, login multi room use different user id or user name. Solutions: Currently supports at most one key, if you need to support multiple, contact ZEGO technical support.
Description: Multi-room mode required. Cause: Wrong room mode been used, e.g. single-room. Solutions: Please use setRoomMode to select multi-room mode before the engine started.
Description: The switchRoom function cannot be used in multi-room mode. Cause: multi room mode SDK not support. Solutions: first call logoutRoom then call loginRoom.
Description: This error code is returned if the user does not pass AppSign when creating the engine or Token when logging in to the room. Cause: The Token is not transmitted in the login room. Solutions: Set the Token when you login to the room.
Description: Update room Token has no push permission. Cause: Token Does not have the push permission. Solutions: Pass in the Token with the push permission.
Description: Room login retry has exceeded the maximum retry time. Cause: Possibly due to network problems. Solutions: Please check whether the network is working or switch the network environment.
Description: The frequency of calls to the interface by users in the room exceeds the upper limit. Cause: The interface is called too often by users in the room. Solutions: Please control the frequency of calls to this interface by users in the room. Please refer to https://docs.zegocloud.com/article/7612 for details.
Description: The number of keys set in the room additional message exceeds the maximum number of supported limits. Cause: called setRoomExtraInfo Different keys have been passed in multiple times. Solutions: please contact ZEGO technical support.
The key for room extra info is empty. The key for room extra info entered by the setRoomExtraInfo function is empty. Please check the key for room extra info entered when calling the setRoomExtraInfo function to make sure it is not empty.
The key for room extra info is too long. The length of the key for room extra info input by the setRoomExtraInfo function is greater than or equal to 128 bytes. Please check the key for room extra info entered when calling the setRoomExtraInfo function to ensure that its length is less than 128 bytes.
The value for room extra info is too long. The length of the value for room extra info input by the setRoomExtraInfo function is greater than or equal to 4096 bytes. Please check the value for room extra info entered when calling the setRoomExtraInfo function to ensure that its length is less than 4096 bytes.
Description: The room ID has been used by other login room interface. Current user can not login room with the room ID before release the room ID. Cause: The room ID has been used by other login room interface. Solutions: Logout the room with the same room ID first.
Description: Haven't login with the input room ID. Cause: Haven't login with the input room ID before call logoutRoom or switchRoom or renewToken or setRoomExtraInfo. Solutions: Please check has login with the room ID or not.
The input room ID contains invalid characters. The room ID entered by the loginRoom function contains illegal characters. Please check the room ID entered when calling the loginRoom function to ensure that it is only contain numbers, English characters and '~', '!', '@', '#', '$', '%', '^', '&', '*', '(', ')', '_', '+', '=', '-', '`', ';', ',', '.', '<', '>', ''.
The input room ID is empty. The room ID entered by the loginRoom function is empty. Please check the room ID entered when calling the loginRoom function to make sure it is not empty.
The input room ID is too long. The length of the room ID input by the loginRoom function is greater than or equal to 128 bytes. Please check the room ID entered when calling the loginRoom function to ensure that its length is less than 128 bytes.
Description: License authentication is used, and when using the relevant function, the license is configured with a functional limitation that does not allow the use of the function. Solutions: Proofread the license's functionality limitations and use the functionality appropriately.
Description: The length of the custom data attached during login exceeded the limit. Procedure. Cause: The login custom callback data is too long. Solutions: The length of user-defined login data cannot exceed 128 bytes.
Description: The business server has sent a signal to kick the user out of the room. Cause: The business server has sent a signal to kick the user out of the room because the internal session was abnormal. Solutions: Contact the business server for processing.
Description: Token Appid error. Cause: The generated Token Appid is inconsistent with the SDK used Appid, Or the appID type is incorrect. Solutions: Use the Appid of the generated Token.
Description: The business server has sent a signal to kick the user out of the room. Cause: The business server has sent a signal to kick the user out of the room because the token expired. Solutions: Please update the token in time after receiving the callback notification that the token is about to expire.
Description: Token Format error. Cause: The generated Token transmission parameter payload is in non-JSON format. Solutions: The payload is correctly transmitted in json format when the Token is generated.
Description: The Token Nonce parameter type is incorrect. Cause: The nonce parameter type of the generated Token is incorrect. Solutions: Ensure that nonce is int64 data.
Description: Token userID error. Cause: The generated Token userID is inconsistent with the login used userID Or the userID type is incorrect. Solutions: Login using the userID that generates the Token.
Description: Token version error. Cause: Description The Token Version was generated incorrectly. Solutions: Generate the Token with the correct version.
Description: The input user ID contains invalid characters. Cause: The input user ID contains invalid characters. Solutions: User ID can only contains numbers, English characters and '~', '!', '@', '#', '$', '%', '^', '&', '*', '(', ')', '_', '+', '=', '-', '`', ';', ',', '.', '<', '>', ''.
The input user ID is too long. The length of the user ID input by the loginRoom function is greater than or equal to 64 bytes. Please check the user ID entered when calling the loginRoom function to ensure that its length is less than 64 bytes.
Description: If the user is in the server blacklist when logging in to the room, this error code will be returned, indicating that it is forbidden to log in to the room. Cause: The user is currently in the server blacklist. Solutions: Please contact ZEGO technical support.
The input user name contains invalid characters. The user name entered by the loginRoom function contains illegal characters. Please check the user name entered when calling the loginRoom function to ensure that it is only contain numbers, English characters and '~', '!', '@', '#', '$', '%', '^', '&', '*', '(', ')', '_', '+', '=', '-', '`', ';', ',', '.', '<', '>', '/', ''.
The input user name is empty. The user name entered by the loginRoom function is empty. Please check the user name entered when calling the loginRoom function to make sure it is not empty.
The input user name is too long. The length of the user name input by the loginRoom function is greater than or equal to 256 bytes. Please check the user name entered when calling the loginRoom function to ensure that its length is less than 256 bytes.
Description: Wrong order of login rooms. Cause: Log in multi room without log in the main room. Solutions: Please log in to the main room with loginRoom before logging in to multi room.
Description: Wrong order of logout rooms. Cause: Log out the main room without log out multi room. Solutions: Please log out of the multi room before logging out of the main room.
Description: Failed to create screen capture source. Cause: The instance exceeds the maximum limit. Solutions: Use an existing screen capture instance or destroy the previous instance.
Description: Startup screen capture failed. Cause: The current system version does not support screen capture. Solutions: Use system version above Android 5 (API level 21).
Description: Startup screen capture failed. Cause: The user refused to grant the app screen capture permission. Solutions: Allow the app to capture screen permissions.
Description: Failed to create dump data folder. Cause: No read and write permission or the disk is full. Solutions: Check to see if there is still space on the disk.
Description: The dump data exceeding the maximum upload limit error. Cause: The dump data is too large to exceed the limit of the upload module. Solutions: Please contact ZEGO technical support and report to ZEGO manually.
Description: Network speed test connection failure. Cause: Not connected to the network. Solutions: Please check if you can access the Internet properly.
Description: The server side ends the network speed test. Cause: Network speed test time is too long. Solutions: Please stop network speed test in 30 seconds.
Description: Network speed test stopped. Cause: Network speed test not stopped before playing stream. Solutions: Please stop network speed test(stopNetworkSpeedTest) before playing stream.
Description: Network speed test stopped. Cause: Network speed test not stopped before publishing stream. Solutions: Please stop network speed test(stopNetworkSpeedTest) before publishing stream.
Description: Invalid system performance monitoring interval. Cause: The set system performance monitoring interval is out of range. Solutions: Please check if the system performance monitoring interval is out of range or not, valid range is 1000, 10000.
Description: Login to the room causes the network test to stop. Cause: Already logged in to the room. Solutions: Since the network test will take up bandwidth, please do it before logging in to the room.