Closed kylekirkby closed 2 years ago
It looks like this issue was due to a space being appended to the Google Client secret... 🤦🏼♂️
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server amplify-help
forum.
Before opening, please confirm:
JavaScript Framework
React, Next.js
Amplify APIs
Authentication
Amplify Categories
No response
Environment information
Describe the bug
I've recently tested the Amplify Hosting product with our development environment. However, since testing, our authentication setup has broken. Firstly, we lost our custom SSO provider details. I'm now getting the following error when trying to authenticate via Google.
This suggests to me that something has changed that means the correct Google Client ID is no longer being provided to the Amplify JS authentication functions. This was working absolutely fine until we recently tested CI/CD via Amplify Hosting.
As I'm writing this, I'm thinking this might be more of an Amplify CLI issue than Amplify JS. Please advise.
Expected behavior
When clicking the "Sign in with Google button", the correct Google Client ID should be provided to the Amplify JS authentication methods.
Reproduction steps
Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response