For many Google Assistant users, the ability to access personalized information is a key part of their smart home experience. Unfortunately, a relatively new bug has surfaced in the past few weeks preventing Google Assistant from displaying personal results on shared devices like smart speakers, Smart Displays, Smart Clocks, and even Pixel Stands.
The issue manifests in a couple of ways. Some users encounter repeated requests to enable personal results in the Google Assistant settings even when the feature is already active (1,2,3,4,5). Others report that the “Personal results” option in Assistant settings is completely missing for them, making it impossible to manage the setting.
As a result, simple commands like checking your calendar or accessing your music library result in a frustrating error message. Instead of providing the required information, Google Assistant states that it needs permission to access personal results in order to serve you with what you asked for.
Typical troubleshooting steps such as toggling the personal results setting off and back on, removing and re-adding Google accounts, and even reinstalling the Home app have proven ineffective. This indicates a larger issue that requires attention from Google. Fortunately, the issue has been picked up by a forum product expert and escalated to the Google Home development team for further investigation and potential fix.
There are others reporting similar. I will go ahead and escalate this
While there’s no word on when a fix will arrive, a user-suggested workaround could provide temporary relief to some affected individuals. Apparently, ensuring that all your devices installed with the Google Home app have the “Personal results” setting enabled, even toggling them off and back on individually, has shown some success. Alternatively, you can as well delete the entire home and start adding your devices from scratch, although this isn’t an ideal solution for people with dozens of smart speakers.
Although not a guaranteed solution, it’s worth trying while awaiting an official fix from Google. We will update this article if and when a fix rolls out.