# Tried Google Social connection with the client id from GCP but get uri\_redirect\_mismatch

**URL:** <https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [December 1, 2023, 4:29pm UTC](https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163 "2023-12-01T16:29:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mirzaam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mirzaam/32/52906_2.png) [@mirzaam](https://community.auth0.com/u/mirzaam)\
**Post date:** [December 1, 2023, 4:29pm UTC](https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163/1 "2023-12-01T16:29:43Z")

</div>

I have been using google social connection without a client id successfully. I then created a 0Auth Client 2 id through GCP to get the client id for my app. I then used the client id in Auth0 Google social connection but I now get an error 400: uri\_redirect\_mismatch. This is an expo app to be used in android and ios, so i set up the client id based on an android app first. I used the SHA-1 key from what i had in my google play store and the package name from my project.  
I have also added [auth0.com](http://auth0.com) to the authorised domain in app registration when setting up in GCP.  
Is there a way of finding out what redirect uri is being attempted here and why its suddenly failing when i use the client id

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [December 4, 2023, 6:23pm UTC](https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163/2 "2023-12-04T18:23:12Z")

</div>

Hi @mirzaam

Welcome to the Auth0 Community!

Thank you for sharing your question! I was going thru logs of the tenant associated with you Auth0 Community Account and I could find any errors or failed login attempts, does this error still occur? Can you generate failed attempts so I can check logs?

Thanks  
Dawid

---

<div class="post-metadata">

**Author:** ![mirzaam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mirzaam/32/52906_2.png) [@mirzaam](https://community.auth0.com/u/mirzaam)\
**Post date:** [December 5, 2023, 9:15am UTC](https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163/3 "2023-12-05T09:15:42Z")

</div>

I was using the android client id and this didn’t work for me. However when I switched to using the web client id and secret it thought the same error and the error details showed me the uri that was missing. Once added the connection was established

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [December 27, 2023, 1:50pm UTC](https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163/4 "2023-12-27T13:50:19Z")

</div>

Hi @mirzaam

Sorry for the late response. It’s great that you managed to solve your issue. Feel free to ask more questions.

Thanks  
Dawid

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 10, 2024, 1:51pm UTC](https://community.auth0.com/t/tried-google-social-connection-with-the-client-id-from-gcp-but-get-uri-redirect-mismatch/122163/5 "2024-01-10T13:51:04Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
