Anonymous Join Exception — production users now get Error 4012

Meeting SDK Web
1

App type: User-managed Meeting SDK app (Web), published to external Zoom users.

Our Anonymous Join Exception was GRANTED in early July 2026 and worked correctly for ~2 months without any issue.

Today (September 2, 2026) this permission is no longer working. We submitted an app update to add the user:read:token scope; after that update was approved, anonymous participant joins in production immediately began failing with:

Error 4012 — AppCanNotAnonymousJoinMeeting (“This join flow is not supported”)

image
image1151×575 15.9 KB

Nothing else changed on our side — no code changes to the join flow. This strongly suggests the republish reset our previously granted Anonymous Join Exception back to a pending state.

Use case (unchanged): viewers are fully authenticated and authorized inside our own platform before reaching the meeting view; the SDK join is anonymous only to Zoom. Meetings are hosted on our users’ own linked Zoom accounts.

Could a member of the team please re-grant / re-activate the Anonymous Join Exception for our currently published version? This is affecting live webinars in production right now. I can share the app Client ID / app name privately if needed.

Thank you.

2

@lvargas I’ll get back to you on this

3

@chunsiong.zoom thank you for picking this up!

Just confirming we’re standing by whenever you have an update. In the meantime
we’re running on a temporary workaround (redirecting attendees to the Zoom
client), but our embedded experience remains blocked without the exception, so
a re-grant would be greatly appreciated.

4

Hi @chunsiong.zoom, following up on this — it’s been about a week since your
last message.

Is there any update on re-granting the Anonymous Join Exception for our
published app?

5

Hi @chunsiong.zoom, any information?