[June 03, 2019 update] Google working to fix Home/Home Mini ‘kGSKErrorDomain’ error

There are new updates that have been added to the bottom of this story…

Original story (from June 11, 2018) follows:

Over the past couple of days, Google Home and Home Mini users have been making efforts to bring to light a new setup related issue – while configuring the Home device (before a successful completion), errors like The operation could not be completed. kGSKErrorDomain Error 0 or kGSKErrorDomain Error 83902 show up.

User shared image of error

The problem apparently affects Google Home/Home Mini users with iOS devices, and is being widely reported across Google Home help forum (1,2,3,4,5,6,7,8) and Google Search and Assistant help forum (1,2).

Take a look at how some of those affected word the issue in question:

I have a issue configuring google home mini. the configuration stops after connecting the wifi and choosing the location (livingroom for instance). I get the message kGSKErrorDomain-0 for the first time then -83902 for the next times.

Hello, I received a google home mini less than a month ago. Having changed boxes I had to reconfigure on our new internet access. but the golds of the configuration arrive at “before using the google assistant” I receive this type of message “the operation could not be completed. (kGSKErrorDomain error 0). After clicking on “OK” the application does not answer anymore I am forced to close it (I use it on an IPhone 6S)

User report of Twitter

Google is aware

What’s appeasing is, following the rising number of complaints, came a statement from a Top Contributor at Google Product forums, saying:

This is a bug that has been reported to the team and they are looking into this.

Google Home help forum expert’s response

But there hasn’t been any follow up from them since then, so there’s currently no info on how long would it take to fix the glitch, thought we hope it gets done soon.

Meanwhile, some of those affected have shared that switching the iOS language to English and then setting up the Home device did the trick for them. So you can try hands on this user suggested workaround until Google comes up with a fix.

Update 1 (June 03, 2019)

If you are suddenly experiencing this problem again, it could be related to the massive Google Cloud outage that happened a few hours ago. If you take a look at the Google services status dashboard, you’ll see several of the services were affected.

Follow @PiunikaWeb

PiunikaWeb is a unique initiative that mainly focuses on investigative journalism. This means we do a lot of hard work to come up with news stories that are either ‘exclusive,’ ‘breaking,’ or ‘curated’ in nature. Perhaps that’s the reason our work has been picked by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and more. Do take a tour of our website to get a feel of our work. And if you like what we do, stay connected with us on Twitter (@PiunikaWeb) and other social media channels to receive timely updates on stories we publish.