How close as a rough estimate because we have a ton of users asking us that our product doesn’t work because of this? We are completely aware of the cadence of Android releases are published and hope to improve this in the future. I would be very surprised if this took 6 months. 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. Waiting for 6 months on this would only increase the frustration of SDK users and possibly every user of Zoom on Android 12. 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. 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. While one individual change may be very few lines of code, the task of adding support for Android 12 is far from trivial.
Mattj stated that there is around 4-5 lines of code needed which shouldn’t be that difficult or take 6 months to implement. 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. We completely understand the severity of the issues that the lack of Android 12 support causes for your end users.
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.Īlso, 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. I.e., if you were hoping to opt in and get all the final features like a system-wide dark mode today, you are out of luck.Hi but this thread will likely close and be locked until another thread on this opens so I doubt we will be updated here. This initial release doesn't have quite as many features as we saw in the previously leaked images, so we assume most of the changes present today are under the hood (API level sort of things) and meant to help developers familiarize themselves with Android Q at a software level. Beta 6 (release candidate for final testing)Īs you should probably have guessed, today's release is Beta 1.Beta 4 (final APIs and official SDK, Play publishing, beta).Google has also added details to its enumerated list of releases, indicating what sort of features might make it into each: Six beta releases are planned in total, with the final release due in Q3. Among the most important is the timeline for beta releases going forward. Today is Android Q day, and behind the scenes we're frantically flashing this new beta to see what's new, but plenty of new details have been revealed officially.
0 kommentar(er)
