Right, @jon.lieblich but this thread will likely close and be locked until another thread on this opens so I doubt we will be updated here.
I can still post and re-open this thread if it locks and will be sure to post here once we have a clearer timeline.
Also, we have got an increasing amount of users who have this issue and the app crashes in front of them that have updated to Android 12, the webinar to be exact in my situation.
We completely understand the severity of the issues that the lack of Android 12 support causes for your end users. Crashes are always the highest priority issues for us to resolve, but we won’t be in a great position to resolve this type of crash until we add full support, unfortunately.
mattj stated that there is around 4-5 lines of code needed which shouldn’t be that difficult or take 6 months to implement.
While one individual change may be very few lines of code, the task of adding support for Android 12 is far from trivial. There are numerous changes in behavior we must account for, in addition to the extensive testing required before we can claim to officially support this OS version. Until all of this work is done to ensure full support for API 31, we cannot fix individual issues that are specific to this version.
Waiting for 6 months on this would only increase the frustration of SDK users and possibly every user of Zoom on Android 12. This OS was released on October (I don’t understand why Zoom didn’t anticipate or test this using the Android beta) so users are now quickly updating to it and complaining.
I would be very surprised if this took 6 months. We are completely aware of the cadence of Android releases are published and hope to improve this in the future.
How close @jon.lieblich as a rough estimate because we have a ton of users asking us that our product doesn’t work because of this?
I don’t think there will be a meaningful amount of time during which a rough estimate will be useful. Once I have a timeline that we are pretty confident in, I will be able to provide an update. We are constantly working on improving our long-term planning that can be shared publicly, so you can definitely expect this to change for the better as time goes on.