# Anonymous Join Exception — production users now get Error 4012 **URL:** \ **Category:** Web\ **Created:** [September 2, 2026, 1:41pm UTC](https://devforum.zoom.us/t/anonymous-join-exception-production-users-now-get-error-4012/146126 "2026-09-02T13:41:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![lvargas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lvargas/32/55638_2.png) [@lvargas](https://devforum.zoom.us/u/lvargas)\ **Post date:** [September 2, 2026, 1:41pm UTC](https://devforum.zoom.us/t/anonymous-join-exception-production-users-now-get-error-4012/146126/1 "2026-09-02T13:41:53Z")
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](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/6/66f3307365a6d70013c2f4786e71aca0585478ef.png) 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. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [September 8, 2026, 5:41am UTC](https://devforum.zoom.us/t/anonymous-join-exception-production-users-now-get-error-4012/146126/2 "2026-09-08T05:41:39Z")
@lvargas I’ll get back to you on this ---
**Author:** ![lvargas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lvargas/32/55638_2.png) [@lvargas](https://devforum.zoom.us/u/lvargas)\ **Post date:** [September 11, 2026, 3:23pm UTC](https://devforum.zoom.us/t/anonymous-join-exception-production-users-now-get-error-4012/146126/3 "2026-09-11T15:23:52Z")
@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. ---
**Author:** ![lvargas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lvargas/32/55638_2.png) [@lvargas](https://devforum.zoom.us/u/lvargas)\ **Post date:** [September 15, 2026, 10:07pm UTC](https://devforum.zoom.us/t/anonymous-join-exception-production-users-now-get-error-4012/146126/4 "2026-09-15T22:07:20Z")
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? ---
**Author:** ![lvargas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lvargas/32/55638_2.png) [@lvargas](https://devforum.zoom.us/u/lvargas)\ **Post date:** [September 23, 2026, 7:10pm UTC](https://devforum.zoom.us/t/anonymous-join-exception-production-users-now-get-error-4012/146126/5 "2026-09-23T19:10:32Z")
Hi @chunsiong.zoom, any information?