amplify-cli: Build Failed - Parameters: [oAuthSecretsPathAmplifyAppId] must have values after upgrading Amplify CLI to latest version
Before opening, please confirm:
- I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- I have searched for duplicate or closed issues.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- I have removed any sensitive information from my code snippets and submission.
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.10.0
Amplify CLI Version
8.3.0
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
auth, function, api, hosting
Amplify Commands
push
Describe the bug
Upgraded Amplify Version to latest and local build and as well as build from Amplify Hosting (CICD) failing with
Following resources failed
× An error occurred when pushing the resources to the cloud
🛑 An error occurred during the push operation: /
Resource is not in the state stackUpdateComplete
Error from CFN stack is
UPDATE_FAILED authelevatehire293576c8 AWS::CloudFormation::Stack Tue May 24 2022 11:05:12 GMT-0600 (Mountain Daylight Time) Parameters: [oAuthSecretsPathAmplifyAppId] must have values
Project does not have any Secrets value configured.
Expected behavior
Amplify Push successful and updated resources in the cloud.
Reproduction steps
- Upgrade to latest version of Amplify
- amplify push
- Observer the error.
Workaround
- Downgrade Amplify CLI - 8.2
- amplify push
- Works fine
GraphQL schema(s)
# Put schemas below this line
Log output
# Put your logs below this line
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 17 (4 by maintainers)
We have reverted the change that caused this issue. Please upgrade to version 8.3.1
This worked for me . @josefaidt , you are a saviour again 👍 🙇♂️
Hey @YuantongL we can step back through
amplify update auth>Walkthrough all configurationsand re-apply the social provider credentials: