Summary:
Our Meeting SDK app was granted an Anonymous Join Exception, and the app shows as fully Activated (not “Active for internal only”) in the Marketplace dashboard following republishing. Despite this, anonymous joins to external meetings (meetings hosted on accounts other than our own developer account) are still failing with the same error we had before the exception was approved. Error observed:
Unable to join this meeting
This join flow is not supported, please join the meeting with a Zoom Client or contact your meeting host or vendor.
Error Code: 4012
What we’ve already checked:
App activation status: confirmed Activated, not internal-only.
“Are you developing a programmatic join use case?” is set to No (our join flow is always human-initiated).
No code or SDK version changes were made between the pre-exception failures and this test — same integration, same build (we also tried with the latest SDK 6.2.0 and we get the same exception).
We followed this thread too but got the same conclusion so far:
@Pierre_Fourgeaud I had to jump onto the Developer Office Hours to get this solved. I don’t recall exactly, but it’s possible the way that it was solved was our app getting added to a manual list somewhere.
I just tested again with the latest websdk and I made sure to use the CLIENT_ID/SECRET for production but we can still not join anonymously calls that are outside our organisation. (We are getting the same error)
