In the wake of the recent Android 16 QPR3 Beta 2 update, Pixel users have found themselves grappling with persistent issues related to Microsoft Office applications. Despite Google’s assurances that the update would resolve previous crashing problems, many users are reporting that the glitches remain, particularly among those operating on the beta version.
Ongoing Issues with Microsoft Apps
The update, which was intended to enhance user experience for Pixel 6 and newer devices, included a comprehensive list of fixes. However, feedback from the community suggests that the promised improvements have not materialized for everyone. Reports flooding in from the Android beta subreddit and Google’s Issue Tracker indicate that the problems with Microsoft apps, including Teams and other Office applications, continue to disrupt daily workflows.
- Some users experience crashes exclusively with certain apps, while others face a broader range of issues.
- In addition to Microsoft Office, complaints have also surfaced regarding the Microsoft Launcher on Android.
One Reddit user, known as bertildator, noted that while their personal profile functions smoothly, the apps crash when accessed through their work profile. This inconsistency raises questions about the root cause of the problem, as other users report similar frustrations across all profiles.
The diversity of experiences complicates the troubleshooting process. While some users, like shinnkuu, have reported no issues with Microsoft apps on the latest beta, others remain mired in difficulties. Google’s initial statement regarding the fix specifically mentioned Microsoft Intune, a cloud service for managing enterprise devices, suggesting that the solution may have inadvertently overlooked the broader user base facing similar challenges.
Interestingly, a potential workaround has emerged from the community. One user claimed to have resolved the crashing issue by re-enabling Android System WebView, which had been previously disabled. However, this solution has yet to be widely verified.
As the situation unfolds, Google has not provided updates on the most active threads in the Issue Tracker, leaving users uncertain about the timeline for a definitive fix. In the interim, reverting to the stable version of Android 16 could serve as a temporary solution, though it may require administrative permissions.
