Hi Zoom team,
Our app has now been approved and published with the Anonymous Join Exception enabled.
App name: MeetingPulse for Web SDK
Client ID: vDIjRI7JRme8VUJVAJ0qHw
Status: Published
Anonymous Join Exception: Enabled in Production
However, anonymous joins are still failing in production for external Zoom meetings.
Could you please confirm whether the exception has been fully enabled server-side for this app, or whether there is an additional propagation/manual activation step required after publication?
This is production-impacting for customers who use MeetingPulse to embed Zoom meetings for HOA, community, church, and accessibility-sensitive meetings.
Thank you,
MeetingPulse Engineering Team
@chunsiong.zoom You were helping us with this same app a few weeks ago, so I wanted to follow up here.
After several weeks and a few review cycles, our app has now been approved, published, and the Anonymous Join Exception has been approved as well.
However, anonymous joins are still not working in production.
Any guidance would be greatly appreciated. We’ve finally made it through the approval process and I’m hoping we’re just one final step away.
Thank you!
Hey, thanks for meeting with us earlier! Just wanted to add some helpful context here for reference.
If you have selected ‘I will manually activate my app’, after your Anonymous Join Exception is approved, you must also manually activate your app for the exception to take effect. If your app is set to manual activation, approval alone is not sufficient.
Please review this doc for guidance on when and how to activate your app:
App Activation – Specific Use Cases
If anonymous joins are still failing after activation, please let us know and we can investigate further!
Thank you @yoon.conner
Upon checking this, and after activation, it is still only working for only meetings created inside of our own Zoom org. (That was actually what I tested on the Dev Office Hours)
Hello @AaronLifshin
I’ll be DM’ing you do get details of the meetings that are failing.
Best,