Skip to main content
New Member
Heena Shingala
New Member
Nov 13, 2026 12:55 PM UTC
Question

Meeting SDK Upgrade – Signature Invalid Error (3712)

We are using the Zoom Meeting SDK for Web in our application.

Our integration was working correctly with Meeting SDK version 3.11.0. However, starting November 7, 2026, we began receiving the following error:

"The current SDK version is no longer supported. Please upgrade to the latest version."

Following the requirement, we upgraded the Meeting SDK from 3.11.0 to 4.0.0. However, after the upgrade, we started receiving a "Signature is invalid" (error code 3712) error when attempting to join a meeting.

We also tried other SDK versions, including 4.1.0, but the same signature error persists.

    1 reply

    TrishGallardo
    Employee
    TrishGallardo
    Employee
    Nov 13, 2026 6:01 PM UTC

    Hi Heena,

     

    Thanks for the detailed breakdown — this helps narrow things down. The "Signature is invalid" error (code 3712) is a signature-validation issue that is separate from the SDK-version upgrade itself, so upgrading the Web Meeting SDK alone wouldn't resolve it if the signature generation isn't aligned with current requirements.

    A few things worth checking in your signature-generation flow:

    • Confirm the meeting number and role in the generated signature match the actual join attempt, and that the token is freshly generated and within the documented time limits.

    • For the Web SDK's join() call, make sure you're passing the generated signature parameter and have removed the deprecated sdkKey join option, since that's no longer part of the current join flow.

    • Double-check the credentials used to generate the signature are current — please do not share your Client Secret, a live JWT, or any other credentials with us when troubleshooting this.

    Separately, on November 8th our monitoring also identified a related issue: a web-side enforcement change raised the minimum supported Meeting/Web SDK version to 4.0, which caused browser-based attendee joins on an older SDK (3.13) to see an "Update Required" message — this was isolated to one internal integration and was rolled back after investigation, but it illustrates that the "no longer supported" version-gating and signature validation are controlled by separate mechanisms, and resolving one doesn't automatically resolve the other.

    Could you confirm:

    1. Whether the signature is generated server-side using your Meeting SDK app's current SDK Key/Secret, and
    2. Whether you've regenerated a fresh signature (not reused one tied to the old 3.11.0 integration) for testing on 4.0.0/4.1.0?

    If the issue persists after verifying the above, please submit a ticket to support.zoom.com and share your SDK version, a sanitized signature payload (no Secret/JWT), and the exact join parameters being passed, and we'll escalate for deeper investigation.

     

    Translate
    Terms & ConditionsAccessibility statement
    Copyright © Zoom Communications, Inc. All rights reserved.