-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OAuthNotConfigureException: oauth param not configured #14107
Comments
Adding the following to amplifyconfiguration.json
changes the error to |
Hi @izner32 thanks for opening this issue. Looking at the Are you manually modifying the configuration file? If so, and if you have configured the social provider correctly, please use Amplify CLI (from reading your post, I presume you are using Amplify CLI instead of Amplify Gen2) to regenerate the configuration file. You can do this by the following: amplify pull |
Hello, The amplifyconfiguration.json and aws-exports.js I had from the post was the one generated by Amplify and I did not modify anything. I already did the Perhaps stuff aren't configured properly on Cognito hence For additional context, I have added the complete reproduction step. |
Thanks for the follow up @izner32 I attempted Since you mentioned in the reproduction steps that you were manually creating and configuring your Cognito User Pool client, I suspect something might've been missed there. Could you inspect the client settings in AWS Console to double check your configurations? If there is not specific requirement for you to manually create the User Pool and client for just using Amplify, I recommend you to create the resource with |
Okay, I made the config below appear by placing a dummy allowed sign-out URL in Cognito and then re-importing the auth. But now, a different error has appeared
|
Hey @izner32 As the documentation states, Expo Go is not supported. But the exception you mentioned in your last comment, was due to a native app scheme URL is missing from the redirect urls in your configuration. Within a react-native app, a |
Before opening, please confirm:
JavaScript Framework
React Native
Amplify APIs
Authentication
Amplify Version
v6
Amplify Categories
auth
Backend
Amplify CLI
Environment information
Describe the bug
I'm encountering an issue while trying to implement Google Sign-In using AWS Amplify in my Expo Go app. When I use
await signInWithRedirect({ provider: 'Google' })
, I get the following error:[OAuthNotConfigureException: oauth param not configured.]
Here’s what my amplifyconfiguration.json looks like:
Expected behavior
After following everything from https://docs.amplify.aws/gen1/react-native/build-a-backend/auth/add-social-provider/ I expect the Hosted UI to show up.
Reproduction steps
Do every step here: https://docs.amplify.aws/gen1/react-native/build-a-backend/auth/add-social-provider/
Set-up social auth provider (Google)
Set-up Cognito on AWS Console
Other else are using the default values.
Configure Auth Category
Going back to Google Developer Console (console.cloud.google.com) -> APIs & Services -> Credentials
Authorized Javascript Origins
andAuthorized Redirect URIs
Installed
npm install @aws-amplify/rtn-web-browser
Run the app in Expo Go
Code Snippet
// Put your code below this line.
Log output
aws-exports.js
Manual configuration
No response
Additional configuration
No response
Mobile Device
iPhone X
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: