Last week, Google rolled out the Android 16 QPR3 Beta 2 update for Pixel 6 and newer models, focusing primarily on addressing a multitude of issues. Among the fixes was a long-standing problem where Microsoft applications would unexpectedly crash on earlier versions. However, despite Google’s assurances that the issue had been resolved, numerous users are still encountering crashes, particularly with work-related applications.
Android 16 beta continues to crash work apps
Reports from users on the Android beta subreddit and Google’s Issue Tracker indicate that the crashing problem persists, even after the update. The impact of this issue appears to vary significantly among users. Some have noted that specific Microsoft applications, such as Teams, crash unexpectedly, while others experience a broader range of application failures. Additionally, some users have reported difficulties with the Microsoft Launcher on Android.
In an intriguing twist, a Reddit user known as bertildator shared that applications function smoothly on their personal profile but crash when accessed through their work profile. Conversely, other users have indicated that crashes occur regardless of the profile in use. This inconsistency complicates efforts to identify a singular cause for the problem.
Adding to the complexity, some users, including Shinnkuu, have reported that they can utilize Microsoft applications without any issues on the latest Android 16 beta, highlighting the unpredictable nature of the situation.
Some users are not facing any issues
When Google announced the fix, it specifically referenced issues related to Microsoft Intune, the cloud-based service for managing enterprise devices such as phones, tablets, and laptops. This raises the possibility that while the fix may have been effective for Intune-configured devices, it may not have addressed the concerns of regular users experiencing similar problems.
Interestingly, one user found a workaround by enabling Android System WebView, which had been disabled on their device. Despite Google’s awareness of the ongoing issues, there has been little recent activity on the most active threads of the Issue Tracker related to this matter. The timeline for a definitive fix remains uncertain, but there is hope that a resolution will be forthcoming.
In the meantime, users facing persistent issues may consider reverting to the stable version of Android 16, a process that fortunately does not result in any data loss.
