Fix the Signature Is Invalid Error (3712)

Fix the Signature is invalid error

The Signature is invalid error, code 3712, means your developer app is not yet allowed to sign guests into the meeting: almost always the Meeting SDK switch is off, the Local Test step was skipped, or the app sits in a different account from the meeting. Switch on the SDK, press Add App Now, check the account, and the error goes away. Your room and your guests' details are fine while you fix it.

What the message means

When a guest's page joins your meeting, your room asks your developer app for a signed pass that says this guest may join this meeting as an attendee. The meeting platform checks that pass. If the app is not switched on for embedding, not activated, or belongs to another account, the pass is refused, and the guest sees Signature is invalid, sometimes with the code 3712.

On this page that platform is Zoom, connected through the Zoom Meeting SDK. Zoom is a trademark of Zoom Communications, Inc. BrandedRooms is an independent product and is not affiliated with or endorsed by Zoom.

While the error is showing, your guests are not lost. They have already left their name and email at the door and are still on your page. When an embedded join fails, the room offers an Open in the app instead link so nobody is stranded, and it records the failure in your host control panel so you can see exactly how many people hit it.

The fix, in order

Work down this list. Most hosts are fixed by the second or third item.

Sign in to marketplace.zoom.us with the account that owns the meeting, not a personal or test login.
Open your General App, go to Features, choose Embed and make sure Meeting SDK is switched on.
Ignore the option labelled Use public client OAuth. It is not the switch, and turning it on does not help.
Open Local Test and press Add App Now. Approve the prompt to activate the app on your account.
Check that the Client ID and Client Secret in your room settings came from this same app.
Run the guest test again on a second device or in a private window.

Less common causes

If the main fix did not clear it, one of these is usually the reason.

The keys were pasted with an extra space or a missing character. Copy them again from the app and paste them fresh.
Someone generated a new Client Secret in the app after you saved the old one. Paste the new secret into your room settings.
The meeting in your room settings belongs to a different account from the app. The room only signs for the one meeting you configured, so update the meeting or build the app in the account that owns it.
The app was deleted and recreated. A new app has new keys; save those in your room settings.

Confirm the fix before guests arrive

Open the room as a guest on a second device and wait in the lobby. Start the meeting in the app as host, then press Start the room. The guest's page should switch to the meeting by itself, joined muted. Your host control panel lists join problems, so you can also check there that no new failures appear.

If the guest now sees Meeting has not started instead, good news: the signature is working. That message means the meeting itself was not started in the app as host, and it has its own short fix.

Keep it from coming back

The signature error tends to return in two situations: when someone tidies up the developer account and switches things off, and when keys are regenerated. Agree on one person who owns the developer app, keep its name obvious, such as your company name plus Room, and add a guest test to your first event checklist so any change is caught the day before rather than at the door.

Frequently asked questions

What causes the signature is invalid error?+

The signature is invalid error means the developer app cannot sign guests into your meeting. The usual causes are the Meeting SDK switch being off, the Local Test step being skipped, or the app having been created in a different account from the one that owns the meeting. Less often, the keys in your room settings are mistyped or out of date.

What does error 3712 mean in my room?+

Error 3712 is the code for Signature is invalid. It means the meeting platform refused the pass your room asked the developer app to create. Switch on the Meeting SDK under Features and Embed, press Add App Now under Local Test, confirm the app is in the meeting's account, and test again.

Can I fix the error without guests noticing?+

Yes, if you catch it during your test. The fix happens in your developer app and room settings, and guests already waiting stay in your branded lobby while you work. After the fix, start the meeting as host and press Start the room; waiting guests' pages switch to the meeting by themselves.

Is my guest data affected by the signature error?+

No. Guests still leave their name and email at the door and wait in your lobby as usual. The error only stops the embedded meeting from opening. Once the developer app is switched on and activated, those same guests join the meeting without entering their details again.