Description
For our android app, we recently upgraded the sdk to version 5.7.1.1267. Since then we have been experiencing a lot of app crashes (242 in the past 2 days) due to a divide by 0 exception in VideoLayoutHelper (screenshot of crashlytics logs below). Is there any solution to this issue?
Sorry to hear you’ve started seeing this crash recently. Have you been able to reproduce this locally at all? Also, are you using a default or custom meeting UI?
From the crash logs, it’s likely webinars are causing the issue; normal meetings are working on our end. Based on the stack trace, sinkUserVideoOrderChanged was called to trigger the crash so this may happen when there are multiple panelists?
Could you help verify if that’s the case? Or is there a way we can setup a webinar without the webinar add-on?
Thanks for the information. We can investigate this based on the stack trace, but it may be difficult for us to identify a fix without the ability to reproduce the crash. I will keep you updated as we look into this, but please let me know if you find anything that could be useful in helping us reproduce the crash.
Thanks for the reply. We’ve been working to reproduce the crash locally but haven’t been successful thus far. This issue is quite urgent for us as we’ve had to disable the SDK for our android users. Do you have any sense of how quickly the crash will be able to get fixed?
Just to follow up with some additional information that may be helpful. From checking the logs of the crashes we found that all of them occur in either the first 15 minutes or the last 15 minutes of the 1.5 hour long webinar.
We still haven’t been able to reproduce the crash yet. Based on the stack trace in the original post is there any information you could give with regards to what may be the issue so we can focus our efforts to reproduce it on our side?
After investigating further, we should be able to at least prevent the crash from happening based on the stack trace. This should be available in the next release of the SDK.
That being said, since we still have not been able to reproduce the crash, we cannot guarantee that this will not cause unexpected behavior somewhere along the way. Please let us know if you are seeing any strange behavior after the fix becomes available.
Just to follow up. Do you have any sense of what the worst case unexpected behaviors we may see after the crash is fixed could be? For example, is it possible the user will be unable to view the stream?
We’ve been able to reproduce the crash. It seems to happen when the user first joins the webinar. It doesn’t happen for all webinars and we don’t know about what’s unique about the webinars that it does happen for. We’ve collected some logs from the sdk for 2 android devices that we reproduced the crash on. The first is a pixel2 xl running android 11 and using sdk version 5.7.1.1267. The second one is a galaxy3 running android 11 with the same sdk version. From our crash reports, it seems the crash happens on all different kinds of devices though. Here is a google drive link to a folder with the logs Zoom SDK Crash Logs - Google Drive.
Thanks a lot! Do you know when we can expect the next release of the SDK?
We actually got pretty lucky with timing on this, and were able to include this in a hotfix release that is available now.
Just to follow up. Do you have any sense of what the worst case unexpected behaviors we may see after the crash is fixed could be? For example, is it possible the user will be unable to view the stream?
We do not have any specific ideas on what behavior could happen. The only thing we know for certain is that this crash will not happen.
We’ve been able to reproduce the crash. It seems to happen when the user first joins the webinar. It doesn’t happen for all webinars and we don’t know about what’s unique about the webinars that it does happen for.
That is definitely good news that you were able to reproduce it! Can you try reproducing it on the new version of the SDK and let me know if there is any unexpected behavior?
It seems to be working well on the new sdk. Thanks for all the help and the quick fix! We’re not sure about this but it seems like the crashes may have been occurring in webinars that enable live transcription.