-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting continuously getting disconnected right after status is connected - (Android & iOS ) #114
Comments
same issue created on zoom portal which is resolved by updating the SDK - check this link |
@evilRat @iamgouravturka any update here? |
Anyone is welcome to use my fork. I've just updated both Android and iOS SDKs to the latest versions (5.14.0): flutter_zoom_sdk: Run the same command after adding the above to your PubSpec.yaml: flutter pub run flutter_zoom_sdk:unzip_zoom_sdk I also added a method: and functionality so that the user does not get asked for details when joining: Please note: this does not work with the iOS simulator. |
I try your implementation, but I get on iOS
|
Hi. I forgot to mention that it does not work on iOS Simulator at all. If this error was on a physical device I will need to investigate. |
@craigspicer This solution worked to join regular meetings. Stuck on MEETING_STATUS_CONNECTING Logs:
|
Hi. You'll need an SDK key and secret. I believe the webinar feature is a paid feature so this needs to be done on Zoom's side. We used webinars in our production app and we had to ensure that we had access to this feature.
|
I was able to join the meeting in past. But, now I'm not able to join the zoom meeting. every time I try to join the meeting it gets connected and then it gets disconnected with toast messages
MEETING_STATUS_CONNECTING
MEETING_STATUS_DISCONNECTING
METTING_STATUS_FAILED
MEETING_STATUS_IDLE
I think this is due to some updates from zoom which need to be accommodated in this package.
@evilRat can you please accommodate the updates from zoom to your package so that it starts behaving as it should?
The text was updated successfully, but these errors were encountered: