I am also able to reproduce this in the sample app. Apologies for the inconvenience, we will look into why this is still happening after including the fix in the release.
Is any new information about it? Because it’s a pretty critical case. I mean there isn’t even any workaround, because there isn’t a way to handle or maybe prevent this exception on our side.
But as I mentioned before default UI flow doesn’t have this issues, so I hope it will be easy to fix it on custom UI flow side.
We actually just released a hotfix version of the SDK that should address this. We will be publishing the release notes shortly, but you can already download the new version through the Marketplace.
When you move a user between breakout rooms or from a breakout room to the main meeting, the sequence of callbacks should be the same. No matter which of these scenarios you encounter, at its core the action taking is moving a user from one meeting instance to another.
yeah, you are absolutely right there is some sequence of callbacks when I try to move the user to the breakout rooms.
but I’m not receiving any callbacks after click on “Main Session” button.
Yes, you are absolutely right, I’m not receiving any callbacks when the admin is clicking on “Main Session” button.
I have put logs into all callbacks of ZoomSDKNewBreakoutRoomControllerDelegate and it’s silent in this case.
@jon.zoom , Hi
The Breakout room crash has not been repeated yet in the new build. Thank you!
But there is a feature request for cancelation flow. I mean we isn’t received any callback in the case when we try ‘leave’ or ignore joining (after onHasAttendeePermission callback receiving).
It would be good in the case when the app should inform the user about the room switching and get his confirmation.
Because in Zoom app (web, desktop) there is an alert that inform the user every time about the room switching.
Glad to hear it! Regarding the feature request, we are still looking into this and do not yet have any updates. Thank you for your patience as we continue looking into this feature request.