This event will be triggered whenever any invalid configuration provided or server/network errors arise, this event will trigger with a specific error code and message.
This event is helpful for development level troubleshooting while integrating SDK.
You can implement this method of the abstract Class MeetingEventListener and add the listener to Meeting class using the addEventListener() method of Meeting Class.
The error object passed to onError() contains three keys:
Key
Type
Description
code
int
Numeric error code, matching a constant returned by VideoSDK.getErrorCodes().
name
String
The error-code constant name, for example "PUBSUB_SUBSCRIBE_FAILED".
message
String
Human-readable reason. For server-reported errors this is the server's specific message when it sends one.
Breaking change in v2.0.0
The payload key type has been renamed to name. There is no compatibility alias — code reading error.getString("type") will no longer find a value and must be updated to error.getString("name"). The code and message keys are unchanged.
This table lists errors that occur due to the configuration and limitations within your organization’s account. These include account status, participant limits, and add-on service availability.
Name
Code
Message
ACCOUNT_DEACTIVATED
4006
Your account has been deactivated. Please contact VideoSDK support.
ACCOUNT_DISCONTINUED
4007
Your account has been discontinued. Please reach out to support for more details.
MAX_PARTICIPANT_REACHED
4009
You have reached the maximum participant limit for this meeting.
MAX_SPEAKER_REACHED
4010
The maximum number of speakers for this meeting has been reached.
MAX_SPEAKER_LIMIT_REACHED_ON_ORGANIZATION
4026
Your organization has reached the maximum number of speakers allowed.
MAX_VIEWER_LIMIT_REACHED_ON_ORGANIZATION
4027
Your organization has reached the maximum number of viewers allowed.
ADD_ON_SERVICES_DISABLED
4021
Add-On services have been disabled. Please contact support to enable them.
MAX_RECORDING_LIMIT_REACHED_ON_ORGANIZATION
4028
You have reached max limit of recording on organization. To increase contact at support@videosdk.live
MAX_HLS_LIMIT_REACHED_ON_ORGANIZATION
4029
You have reached max limit of hls on organization. To increase contact at support@videosdk.live
MAX_LIVESTREAM_LIMIT_REACHED_ON_ORGANIZATION
4030
You have reached max limit of livestream on organization. To increase contact at support@videosdk.live
MAX_RECV_ONLY_LIMIT_REACHED_ON_ORGANIZATION
4041
Your organization has reached the maximum recv-only limit. To increase contact at support@videosdk.live
Errors listed here are related to issues with the API key, authentication tokens, or permissions assigned to users. These errors can occur when tokens are missing, expired, or improperly configured.
Name
Code
Message
INVALID_API_KEY
4001
The provided API key is either missing or invalid.
INVALID_TOKEN
4002
The provided token is empty, invalid, or has expired.
INVALID_PERMISSIONS
4008
The permissions in the token are incorrect. Please verify them.
UNAUTHORIZED_MEETING_ID
4022
The provided token is not authorized for this meeting ID.
UNAUTHORIZED_PARTICIPANT_ID
4023
The provided token is not authorized for this participant ID.
UNAUTHORIZED_ROLE
4024
The role specified in the token is not valid for joining this meeting.
UNAUTHORIZED_REQUEST
4025
Your request does not match the security configuration.
APIKEY_DEACTIVATED
4053
The provided API key is deactivated. Please verify it on the dashboard.
3. Errors associated with Meeting and Participant
This table lists errors resulting from invalid or missing meeting or participant details, including cases where a participant attempts to join with a duplicate ID.
Name
Code
Message
INVALID_MEETING_ID
4003
The meeting ID provided is either invalid or missing.
INVALID_PARTICIPANT_ID
4004
The participant ID is either invalid or missing.
DUPLICATE_PARTICIPANT
4005
This participant has joined from another device.
MEETING_ID_DISABLED
4052
The provided meeting ID is disabled. Please generate a new meetingId using the API.
These errors are triggered when an action cannot run in the current state — called before the meeting is joined, while it is reconnecting, or when the SDK cannot reach the VideoSDK servers in time. The delivered message names the rejected method when available; the messages below are the fallback text.
The meeting is reconnecting. Please try again once it reconnects.
ERROR_OPERATION_ABORTED
3015
The operation was aborted before it completed.
ERROR_ALREADY_IN_REQUESTED_STATE
3016
The requested state is already active.
8. Errors associated with Participant and Meeting
These errors are triggered when the server rejects a request that targets a remote participant or changes the meeting — including stream subscriptions, meeting mode, room switching, and media relay. The state stays as it was.
These errors are triggered while using in-meeting collaboration features such as PubSub messaging, the realtime key-value store, the whiteboard, and translation.