Failed to authenticate with Google...?

My problem is the same as Robert Bannister and we are obviously looking through all the same threads and not getting an answer.

Who gives an F about Clock and Time, this is about Google and gmail and the pane the keeps asking for password.

I'm getting the same "Google Password Required..." message too, and can't get past the Authentication Failed message either. At first the banner only came up about every 10 minutes, now it comes up every few seconds. It's driving me mad.

Try deleting the google account from Internet Accounts in System Preferences, then add it again. It worked for me.

Yep - that sorted it for me as well - see my original post > Apr 27, 2015 3:29 AM

I deleted the account and restored it. That eliminated the authentication request. However, iCal is continuing to experience lots of problems. Long delays loading, repeatedly, despite quitting and restarting the program

I'm having the same issue with one particular google account. Strangely I have several other gmail accounts (personal and work) that are working fine. However this one gmail account constantly states that I need to reenter my password. This happens on across my Apple devices that all have the latest operating system 10.10.3 OS X and 8.3 iOS. I constantly get the "Google Password Required" that ultimately results in "Failed to authenticate with Google." I've deleted and tried to add the account to no avail. It still pulls in new email and I can archive/delete the emails, however I can't send any emails from that account.

Who do we direct our frustration to, Apple or Google? Doesn't seem like there is any support provided by Google to assist with these issues.

Apple will just say it is you not them. I have tried this with every problem since OS9 and it's the same each time.

I did delete gmail from system preferences and all google/gmail calenders. Emptied trash, restarted, and the popup to enter password for gmail in System Preferences has recurred three times since looking in the threads to see if an answer has been delivered.

There is at least one other thread about this issue and from there, I was given the tip. Go to sytems preferences>internet accounts and delete Google. Later, put Google back in again, type in the email address you actually use (I don't use gmail even though I have an address) and you password, and hey presto.

I have the same problem- a notification appears saying 'Google Password required', so i follow the steps -continue -to a page titled Internet accounts, listing iCloud, and two google accounts. I have a separate gmail account, and a .mac, .me, .cloud account that are all aliases of my original mac.com account. It asks me to sign in to my gmail account, accepts my password, spins for bit, a mysterious page with some code appears for a milisecond, and then the 'authentication failed' appears. I am able to access my mail, and the internet, but the notification is annoying at best and worrisome. I too recently upgraded to OS X....

Deleting the 'offending' account solved the problem for me - the thing is i have several alias emails based on my original mac.com address. one of those was what i had to delete. I have no idea how to 'restore' it, but i still get emails at that address as well as the original account and all the other versions (mac.com, me.com, cloud.com, plus two different personal prefixes.

Who knows why?

It's a mysterious Apple/Google world and i often feel like Helen Keller - but look what she accomplished! i try not to be faint of heart.

I deleted the offending account too, then added it back in, and have lost all of my calendar entries. 😠 It's not vital, I was able to find all upcoming appointments and re-enter them, but I often need to check back to see when some event or other last occurred and I can no longer do that. On the plus side, I haven't seen any more annoying messages about entering my password.

I've been dealing with the same issue after an upgrade from 10.6 to 10.10, although in my case there's the additional and possibly relevant hitch that my Google accounts are through a university's Google Apps service, so the standard Google login page always gets redirected to a University page to authenticate before sending you back to Google (regardless of whether you log directly into a Google service on the web or through an Apple app).

Oddly, I was still getting my email, and my calendar (both of which were configured prior to migrating) was also updating, despite the constant failed login errors.

I tried the suggestion of deleting and recreating the account, but that did not work. Re-creating the account failed on the same error.

I managed to get my email working again by adding it through Mail.app as a generic account, although the System pref pane recognized it as a Google account, and then started throwing the same errors.

After clearing caches, doing permissions fixes, and a few reboots, I spent some time staring at common log errors and noticed that both IdentityFinder (a university-supplied app that searches your drive for passwords, SSNs, and other identifying info you might have saved in cleartext) and Microsoft EndpointService (a virus scanner) were crashing and throwing oddball errors, respectively, in a steady stream.

I started with IdentityFinder and eventually managed to dig it out of LaunchServices, and after a reboot those errors stopped, the EndpointService errors stopped inexplicably as well (might have been an auto-update in there or something), and now I'm not getting the Google login errors. Whether it was removing IdentityFinder, fixing whatever the Ms virus scanner was doing weird, or something completely unrelated, something in there apparently fixed it. I'm reluctant to try deleting and recreating the account to confirm that it's 100% fixed, but it's strange that apparently unrelated things were interfering with this (maybe the virus scanner was interrupting the confirmation dialogue?).

That's interesting, although a nuisance for you. I deleted Google, put it back again and my Mac calender is unaffected. I don't use the Google one anyway.

Yes, interesting. But I've given up trying to get it right or trying to figure out why it happened - it makes my hread hurt!

This worked for me. Thank you!