HomeBreadcrumb ArrowModulesBreadcrumb ArrowOpenCartBreadcrumb ArrowGoogleLoginBreadcrumb ArrowFatal error: Uncaught exceptio...
Thread Solved

Fatal error: Uncaught exception 'Google_AuthException'

This discussion has been marked as solved
User Image
Maximilian member
#1 posted on 23/1/14 (edited on 23/1/14)

Hello,

I get this error, when I try to login with Google:

Fatal error: Uncaught exception 'Google_AuthException' with message 'Error fetching OAuth2 
access token, message: 'redirect_uri_mismatch'' in /homepages/19/d18876676/htdocs/vendors/google-api/auth/Google_OAuth2.php:113 Stack trace: #0 /homepages/19/d18876676/htdocs/vendors/google-
api/Google_Client.php(131): Google_OAuth2->authenticate(Array, '4/Qfqe51nJS6m2D...') #1 /homepages/19/d18876676/htdocs/catalog/controller/account/googlelogin.php(35): 
Google_Client->authenticate('4/Qfqe51nJS6m2D...') #2 [internal function]: Controlleraccountgooglelogin->index() #3 /homepages/19/d18876676/htdocs/vqmod/vqcache
/vq2-system_engine_front.php(47): call_user_func_array(Array, Array) #4 /homepages/19/d18876676/htdocs/vqmod/vqcache/vq2-system_engine_front.php(33): Front->execute(Object(Action)) #5 
/homepages/19/d18876676/htdocs/index.php(237): Front->dispatch(Object(Action), Object(Action)) #6 {main} thrown in /homepages/19/d18876676/htdocs/vendors/google-api/auth/Google_OAuth2.php on 
line 113

You can take a look at the shop here: https://www.bear-speed-parts.de/index.php?route=account/login

Thanks!

0
User Image
Maximilian member
#2 posted on 23/1/14

Solved the Problem, the Redirect URI is with https, but the module sent it to google http.

In the \catalog\controller\module\googlelogin.php in line 22, I replace "$redirect = $this->url->link('account/googlelogin');" with "$redirect = "https://www.bear-speed-parts.de/index.php?route=account/googlelogin";" and it workes fine.

Looks like a bug...

0
User Image
Nikola Hristov member
#3 posted on 23/1/14

Thank you for reaching us.

Glad you have worked it out.

This has been logged in our development system and it is going to be fixed in the next version of GoogleLogin.

0