-
Notifications
You must be signed in to change notification settings - Fork 825
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
@aws-amplify/[email protected] breaks build: Failed to pull the backend. auth headless is missing the following inputParams facebookAppIdUserPool, facebookAppSecretUserPool, googleAppIdUserPool, googleAppSecretUserPool #4790
Comments
workaround: fallback to 4.21.3
|
Hello @bwalsh |
I am suddenly getting the same error. |
yep me too |
Previous builds with the CLI would fail on a push as the social provider credentials were not available in the project on doing a pull. This was an issue in #3642 by adding those hosted credentials on a pull this would avoid a failed push. Ref Issues |
My fix:
Then in the Amplify console add the environment variables:
|
Puzzled. Why client id's and secrets needed when they already exist in cognito? Thought the point of pull was to retrieve that from stack. Our build simply deploys the app, does not make changes to auth. |
same here. my temp solution was to downgrade cli version to |
I finally resolved that issue. even though it is temp fix... here is my comment in issue |
@bwalsh Correct though to change credentials we expose this value. We realize this workflow isn't convenient as you would need to resend the credentials. In the long term we are looking at changing this, as noted in aws-amplify/amplify-hosting#206 (comment). Closing this issue. Should you experience any other issues related to the auth config on the CLI please comment below to re-open. |
Worked for me! |
Same issue. Using social federation with facebook, google, and amazon. Never had this issue until upgrading recently. I believe it was 4.22 that broke my code. The credentials were properly set up through the cli and have not changed since. I have CD set up through the amplify console. Again, not sure why my pushes are failing now since they never have before. If anyone could elaborate on whether or not this will be fixed, or if in fact this is not a bug, that'd be great edit: I was able to temporarily fix this issue in a similar way as @bwalsh Before
After
|
Hi there, how did you generate the values for the following variables?
|
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 |
Describe the bug
Version change broke our production deploy
Amplify CLI Version
@aws-amplify/[email protected]
To Reproduce
Expected behavior
The pull command to complete
Screenshots
Desktop (please complete the following information):
NA default build container
The text was updated successfully, but these errors were encountered: