-
Notifications
You must be signed in to change notification settings - Fork 820
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
Parameters: [auth#appname#IdentityPoolId] do not exist in the template #13797
Comments
Hi @PeterSchoell 👋, thanks for raising this issue.we are working on reproducing the issue. Could you please run below command and send us the project identifier |
Project Identifier: 1665dd35b4fc64548f5cf355f7fb1828 Thank you very much for the quick reply! |
Hi @PeterSchoell, Thank you for providing the diagnose report. I'm going to transfer this over to our CLI repository for better assistance. |
Hey @PeterSchoell, Could you provide us some additional information on the update made on the auth resource such as prompts selected and inputs provided. This would assist in reproducing the issue. |
I have redone many settings, rebuilt and pushed some things. The result was that everything worked again at some point. Unfortunately, I cannot provide any further details. The problem must have taken me two weeks. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v21.5.0
Amplify CLI Version
12.12.0
What operating system are you using?
Microsoft Windows 10 Business
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made.
Describe the bug
When attempting to update the auth category of a project the deployment fails with the following error.
Expected behavior
The auth category changes can be deployed
Reproduction steps
Have an Amplify project with auth category
Make some change to the auth
Run amplify push -y.
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: