Google Home app users are facing an unexpected technical issue, where the app asks some users to log in or complete the setup process again every time the app is opened, as if they were using the service for the first time.
Reports about this bug began appearing since mid-October via technical discussion platforms such as Reddit and Google support forums. Reports indicate that the problem appears in specific versions including v4.34.22 and v4.35.25.1, and although the bug does not appear to be widespread, it causes significant inconvenience to those affected who rely on the app to manage their homes.
What changes in practice?
This bug goes beyond mere minor inconvenience; it directly affects the smoothness of smart home management. Instead of quick access to the familiar dashboard, users are forced to deal with welcome screens and re-selecting accounts every time. Some users also reported experiencing delays of up to 10 minutes in the appearance of connected devices when attempting to bypass the setup process.
Furthermore, this behavior leads to the disabling of the quick device control feature via the lock screen, which is one of the core functions that system users rely on for immediate control of their smart environment without needing to fully unlock the phone.
Current Status and Proposed Solutions
So far, Google has not issued an official statement confirming the existence of this bug or explaining its causes, despite claims from users that the company's support has acknowledged the problem following a recent app update. In the absence of an announced official solution, some steps emerge that those affected can try:
- Update the app: It is advised to check the Google Play Store and install version 4.36.24 or later, as it is believed it may address the issue, although this has not been officially confirmed by the company.
- Monitor updates: Since the problem is linked to specific versions, following periodic updates may be the only way currently to bypass this software behavior.
The root causes behind this behavior remain unclear, and the technical community is waiting for an official response from Google to clarify whether a comprehensive fix is under development or if the matter relates to an account synchronization bug.