Google is investigating Android 14’s multiple profile update bug

Google is looking into a bug in Android 14 that was wreaking havoc on people with multiple user profiles. On October 27 a A Google representative admitted The error was confirmed and he said the team was “working hard to fix it.”

Thank you for staying with us. Our team is looking into this storage issue affecting some Pixel devices running Android 14 and we’re working hard to fix it. We will update this topic with more details soon.

On October 29, Google’s community manager introduced Additional update About this issue, which they say affects some Pixel 6 models and later. According to the notice, Google continues to “work on fixes” and expects an upcoming system update to “fix the issue and restore access to media files without requiring a factory reset.” It also looks into how to recover data on devices stuck in a boot loop.

Although Google has released a Google Play system update that it says should help prevent the issue from appearing on more devices, the company is recommending that Pixel owners who are not currently affected avoid creating or signing in to secondary user profiles on their devices until the fix is ​​resolved. The complete. They were released.

While the first reports were mostly from Pixel 6 owners who encountered the issue as the update began rolling out, Ars Technica This week I reported that Google’s issue tracker for the issue had surpassed more than 350 responses, spanning owners of many different devices. Issues range from missing apps to constant crashes to locking out the entire internal storage on one of the user accounts on their device.

So far, the issue tracker has more than 510 responses, with some users pasting log files or uploading images of the phone’s screen. several Users They said they couldn’t provide screenshots on the device because the phone reported no storage space available to save them to. Many of them likened the experience to being infected with ransomware.

Updated October 30, 5:59 a.m. ET: Updated with additional Google statement of work to fix the issue.