![]() We are a health app, and have hundred of users and thousand of patients affected by this issue, and we have hospitals too, so is critical to resolve it. However, the same problem is happening with the Meeting SDK to the review team (review team uses accounts that can bypass the external account limit for unpublished apps, so that it’s not the problem), and we need to resolve the issue before publishing the Meeting SDK and remove the old OAuth app from the marketplace. So we adapt all our keys and integration to the new Meeting SDK app, and start the review process to publish to the marketplace. ![]() When we saw this, we thought that the problem was that the old setup (published OAuth app + unpublished SDK app) now need to be done only with the Meeting SDK app, that integrates both functionalities. So now we have both, SDK Key & SDK Secret, and Client ID & Client secret, all in the same Meeting SDK app. In the developer marketplace when accessing the Meeting SDK app, a dialog was prompted to us requesting to update it to the new version with OAuth 2.0 integrated. When it stopped working, we saw that the old SDK app now it’s called Meeting SDK app, and thought that maybe we need to update it. ![]() As same as that thread, there is no error code presented, or error callbacks fired. When the host join in the Client View to the meeting created by the API with the signature and ZAK, that dialog prompts: Joining meeting timeout. That setup was working well until a month ago, when external users started to see the same problem of that thread. That was the way of doing this flow in 2022, a standalone OAuth app that need to be in the marketplace, and a standalone SDK app that don’t need to be in the marketplace. However, there is no problem when we use our own account and managed sub-accounts, the problem is only with external accounts.įrom 2022 until the last month, we had a published OAuth app in the marketplace for the API calls to create / delete meeting and ZAK retrieval, and an unpublished SDK app for an integrated Client View to connect the created meeting as host / attendees. The only difference is that for us, the error is not random and sporadic, it’s happening every time a external Zoom account try to join the meeting as host. We have almost exactly the problem described in this thread. Once you’ve customized your settings, click on “ Save” to create the planned Zoom meeting.We has been requested by Zoom review team to post our problem in the devforum to solve it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |