Crash while I move the user from one breakout rooms to another

Desktop Client SDK macOS
#1

Hi!

Problem: I have gotten the crash while using ZoomSDK demo project.

There is some easy flow to reproduce the crash using ZoomSDK demo project:

Preparing: Start the meeting with a breakout rooms support.

ZoomSDK Demo project side:

  1. Start the example demo app
  2. Enter a domain and check “Custom UI”, click Connect
  3. Enter a jwt, click Auth
  4. Switch to “Join Only” tab
  5. Enter the Info and join
  6. Go to Zoom application side.

Zoom application side:

  1. Open Breakout Rooms dialog
  2. Create several rooms
  3. Open All Rooms
  4. Assign the user to first one room
  5. Move the user to second one room

After 5 step I always get something like: Thread 1: EXC_BAD_ACCESS (code=1, address=0x0)

#2

Hi @anton.yereshchenko, thanks for bringing this to our attention.

I have been able to reproduce this successfully. We will investigate this crash and identify a solution in the future.

Thanks!

1 Like
#3

@jon.lieblich Thank you!

#4

You are very welcome, thank you for continuing to bring things like this up to us! :blue_heart:

#5

Hi, @jon.lieblich!

We have updated ZoomSDK up to v5.5.12509.0330 version.

Fixed an issue where the app crashed when switching attendees between breakout rooms

But this exception is still appears for custom UI flow.
I just have repeated the steps that I have provided above.

#6

Hi @anton.yereshchenko,

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.

Thanks!

#7

@jon.lieblich Hi!

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. :crossed_fingers:

Thanks!

#8

Hey @anton.yereshchenko,

No news quite yet. Hope to provide some soon.

Thanks!
Michael