Unable to Join Meeting (Error Code: 13296) when joining meetings created by another Zoom account

Meeting SDK Type and Version

  • Meeting SDK: Android
  • Version: 7.1.0 (41100)
  • Authentication: SDK JWT Signature

Description

We are experiencing an issue when joining meetings using the Zoom Meeting SDK.

Our Meeting SDK app is associated with Account A.

  • If a meeting is created by Account A, our application joins the meeting successfully.
  • If the meeting is created by another Zoom account (for example, Account B or Account C), the Meeting SDK fails to join the meeting.

This behavior started recently. We have not made any changes to our Meeting SDK integration.

The same meetings can be joined successfully using the official Zoom desktop and mobile applications.

We would like to know if there has been any recent change regarding cross-account meeting joins or if any additional configuration is now required.


Error


Unable to Join the Meeting
Error Code: 13296

Screenshot attached.


Troubleshooting Routes

  • Updated the Meeting SDK to the latest version (7.1.0 (41100)).
  • Verified that the Meeting ID and passcode are correct.
  • Tested with multiple meetings.
  • Confirmed that meetings created by Account A work successfully.
  • Confirmed that meetings created by Account B and Account C fail with Error Code 13296.
  • Verified that the same meetings can be joined using the official Zoom desktop and mobile applications.

How To Reproduce

  1. Initialize the Android Meeting SDK using an SDK JWT Signature.
  2. Join a meeting created by Account AWorks.
  3. Join a meeting created by Account B or Account CFails with Error Code 13296.

Questions

  1. Does the Android Meeting SDK support joining meetings hosted by a different Zoom account?
  2. Has there been any recent change affecting cross-account meeting joins?
  3. What does Error Code 13296 indicate?
  4. Is there any additional configuration required for this scenario?

Any guidance would be greatly appreciated.

Thank you.

@Sri_Sri_Publications are you using OBF token when joining these meeting?

We have the same issue.

We have a large number of students who join Zoom meetings directly inside our app using the Meeting SDK. We also have many instructors who use their own Zoom accounts to host sessions for those students.

Everything was working correctly, but suddenly it stopped working. Students can no longer join meetings inside our app, even though nothing has changed on our side.

Hello @VClasses

Thank you for reaching out.

We recently enforced a requirement for Meeting SDK apps to use OBF or ZAK tokens when joining external meetings — more details here: Transitioning to On Behalf Of (OBF) tokens in Meeting SDK apps - Zoom Developer Blog

If your use case cannot support implementing OAuth to obtain these tokens, an exception may be available — but whether it applies depends on your specific situation and reasoning. To have it evaluated, please submit your app with the “Request Anonymous Join Exception” toggle enabled under Features > Embed > Meeting SDK, and include a clear explanation of your use case in the provided text field.

Our team will review the request from there.

Best regards,

Hi, @yoon.conner @chunsiong.zoom currently I encounter the same issue: the user can’t join meetings from an external account. My app is using the General App instead of the SDK or OAuth app. When I tried to add a scope, I only found user:read but I can’t find user:read:token scope for my app.
Also, how can I test the implementation of the OBF token on my Development environment since an external account can not access my app in the development environment?

@simudin the application must be published for this scenario.

@chunsiong.zoom Which scenario are you referring to? For getting the new scope `user:read:token` to appear on my app scope, or external account can acces my app?

@simudin the application must be published for external account join. In addition to publishing, you need to make sure you are using OBF token in the SDK as part of the join parameters. If not you will not be able to do external account join.

To get the OBF token, you can refer to this article Transitioning to On Behalf Of (OBF) tokens in Meeting SDK apps - Zoom Developer Blog

I’ve just checked on marketplace, and can confirm that user:read:token appears in my marketplace app. This is a general app, user-managed app

@chunsiong.zoom Hmmm weird. It did not shown on my General App. Am i missed something?

Can you help to check why the scope is not shown if i DM you My App?

@simudin you can migrate to granular scopes

@chunsiong.zoom migrating to granular scope wont delete my currently selected scope, right?

@simudin no it should not. Do note after selecting the additional scopes, the application will need to go through review and approval process again for newly selected scopes to take effect.

It will not affect the existing approved app during this process.

Thank you @chunsiong.zoom I just confirmed the `user:read:token` scope is showing now after I migrated to granular scope.