I’m experiencing a consistent initialization failure with Zoom Meeting SDK v6.2.5 on our Android wearable device application. The issue began suddenly on March 18th, 2023 - working perfectly in the morning but failing consistently since the afternoon (Japan Standard Time, UTC+9).
Technical Details:
SDK Version: Zoom Meeting SDK v6.2.5 for Android
Error Message: “Failed to initialize Zoom SDK: 5, internalErrorCode=124”
Timeline: Working until March 18th AM JST (approximately before UTC 03:00), failing since March 18th PM JST (approximately after UTC 03:00)
Reproducibility: 100% reproducible - occurs every time we attempt initialization
I’ve verified the issue using scrcpy to monitor the device screen, which clearly shows the error popup. No code changes were made to our application between when it was working and when it began failing.
Questions:
Were there any server-side changes or updates to the SDK infrastructure on March 18th (UTC) that might explain this sudden failure?
What does error code 5 with internal error code 124 indicate specifically?
Are there any recommended troubleshooting steps for this specific error combination?
Has anyone else reported similar initialization failures with v6.2.5 on wearable devices recently?
Any guidance would be greatly appreciated as this issue is blocking our users from accessing critical functionality.
I’d like to provide additional context regarding our authentication method. Our application uses JWT authentication when initializing the Zoom SDK. We’ve been using the same JWT authentication configuration both before and after the error started occurring, with no changes to authentication credentials (keys or secrets).
I hope this information helps in identifying the issue. Please let me know if you need any further details.
We are still experiencing the same issue with error code 5 (internalErrorCode=124) when initializing the Zoom Meeting SDK v6.2.5 on our Android wearable application.
I would like to respectfully highlight that:
Our application successfully passed the Zoom SDK review process and was functioning correctly until March 18th.
No changes were made to our implementation, or any other aspects of our code prior to this sudden failure.
The issue occurred abruptly without any warning notifications, error logs, or deprecation messages that would have allowed us to prepare for or prevent this service disruption.
We understand that systems evolve and policies change, but we are puzzled by the lack of communication regarding what might have triggered this sudden failure.
As a developer partner who has followed Zoom’s guidelines and review processes, we would greatly appreciate:
Any insights into what might have changed on the backend that could affect approved applications
Specific guidance on how to address error code 5 (internalErrorCode=124)
Information about any recent policy or technical requirement changes that might affect SDK initialization
After receiving assistance for the linked inquiry, I was able to press the submit button, and surprisingly, this also resolved the issue described in this inquiry.
What might have been the cause of this issue? I’m curious to understand the root cause of these interconnected issues.
I hope this message finds you well.
I am reaching out again regarding my previous inquiry.
To prevent similar issues in the future, and to assist others who may encounter the same problem, I am eager to understand the root cause.
Your support in this matter would be greatly appreciated.