Persistent Error 3712 (Invalid Signature) after downgrading the plan

Meeting SDK
1

Hello,
We are reaching out to resolve a persistent 3712: Invalid Signature error within our production environment.

Account Context:

  • Application 1: Used for OAuth flow, Meeting Creation/Deletion/ZAK token/etc. (working as expected now)

  • Application 2: Used only for joining the meeting via Meeting SDK by Host and participants

  • Status: Both applications are fully approved, published, and active in the Zoom Marketplace.

The Issue: Until recently, our integration functioned correctly. Following a recent downgrade of our pricing plan, today we noticed that the Meeting SDK has stopped allowing users to join meetings. When attempting to join a meeting - including meetings created by and hosted on app owner account itself - the Web SDK returns the following error: {method: 'join', status: false, result: 'Invalid signature.', errorCode: 3712, errorMessage: 'Signature is invalid.'}

Troubleshooting Already Performed:

  1. Credential Verification: We have confirmed the sdkKey and sdkSecret are correct and pulled directly from the published Meeting SDK app.

  2. JWT Validation: We have verified the signature payload (HS256)

  3. Cross-Account Isolation: We have tested joining meetings owned by the same account that owns the SDK App, yet the error persists.

  4. Scope/Status: Both apps show as “Active” in the Marketplace dashboard.

Request: Could you please investigate why this error is persisting and provide us with the specific technical steps required to resolve this discrepancy?

We are looking forward to your prompt assistance in restoring our service. Thank you in advance.

2

Hi @Bizzabo ,

Which platform and client version are you experiencing this issue with please? What pricing plan did you change from and to?

4

Hi Gianni,

we are using 3.8.10 Meeting SDK for web. We discontinued ISV contract and now have Basic Plan.

5

Hi @gianni.zoom

Do you have any information related this issue?

6

Hi @gianni.zoom ,

Following up again as our production app has been broken at least for two weeks with no changes on our end. We provided the requested SDK version 11 days ago and urgently need a technical update or a path to resolution, as this is now a prolonged outage for our users.

Could someone from the team please prioritize this investigation? Thank you.

7

Hi @Bizzabo , thank you for your patience! I’m messaging you for the production client id and SDK logs and I’ll open up a ticket for you. Please note the forum is for community-assisted help and we try our best to get to you within a short time window, but for SLA support we recommend our premier developer support.

8

Hi - this won’t be necessary as we decided to end-of-life our integration with Zoom