Beta app: sign-in works for all users, but meeting join/start fails for non-owner (external) accounts
Our app has been approved for beta testing. We’re using the Device Code Flow to sign users in and retrieve their access token, which we then use to fetch their upcoming meetings. We’re also using the Meeting SDK for Android to let users start meetings — passing in their ZAK (fetched via the REST API using their access token) along with the meeting ID.
For context on terminology: I’ll refer to the account that owns the app in the Marketplace (the account I’m posting from) as the owner, and any other Zoom account signing into our app via the Device Code Flow as external.
Owner account: everything works as expected.
- Sign-in works
- Meetings are fetched correctly
- Can start their own meetings
- Can join meetings they’re invited to
- Can start instant meetings (created via the Create Meeting API, then passing that meeting’s credentials to the SDK)
- Can start a meeting using their PMI (fetched via REST API, passed as the meeting ID to the SDK)
External accounts: inconsistent and partially broken.
- Sign-in works, meetings are fetched correctly
- They are not able to join meetings they’re invited to
- Some accounts are not able to start their own meetings, start an instant meeting, or start a meeting via PMI — using the exact same flow that works for the owner account
- This is inconsistent across external accounts: some can start instant meetings, others can’t
Question: If we publish the app and set it to Unlisted, would that resolve these issues? My assumption is this is related to cross-account join/session policies, but I’m not sure if that’s the actual cause or if something else is going on. Any insight would be appreciated.