This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Currently experiencing this same issue. Had Google Assistant working on Sonos Beam previously but last night it stopped working. It would open up when I said "Hey Google" but then would not respond to any voice commands. Tried restarting and disconnecting and reconnecting Google Assistant to see if that would resolve the issue, but now I'm stuck with getting this same error.
I am having the same issue trying to connect my Phillips Hue bridge to Google Home. It looks like it might be a problem with Google’s authentication for connecting apps (OAuth).
It gets stuck at [url-custom=https://oauth-redirect.googleusercontent.com/r/ID?code=code&state=STATE]https://oauth-redirect.googleusercontent.com/r/[SOME_RANDOM_ID]?code=
I tried with my Sonos and for the same exact message. Looks like something on the Google side?
I am having the same issue trying to connect my Phillips Hue bridge to Google Home. It looks like it might be a problem with Google’s authentication for connecting apps (OAuth).
It gets stuck at [url-custom=https://oauth-redirect.googleusercontent.com/r/ID?code=code&state=STATE]https://oauth-redirect.googleusercontent.com/r/[SOME_RANDOM_ID]
?code=
I Googled the message and arrived here. I tried with my Sonos account and got the same message. Looks like something is broken on the Google Home side?
Once you hit the error message, hit the back arrow, then click the little safari icon (compass, bottom right). Will open same error message in safari. Hit back arrow, will take you to sonos sign in. Follow the process....
Once you hit the error message, hit the back arrow, then click the little safari icon (compass, bottom right). Will open same error message in safari. Hit back arrow, will take you to sonos sign in. Follow the process....
Worked for me. Good luck!
That seemed to work! Well at least a variation of it. I didn’t get the option to open in safari, but the first time I got the message I hit back and then just hit submit again and it worked!