the Backend points to a different env

[CLu1s]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting questions.
• [X] I have removed any sensitive information from my code snippets and submission.

App Id

dcg64l50n907n

AWS Region

us-east-1

Amplify Hosting feature

Backend builds

Question

How do I change or confirm where my backend API and authentication are pointing?

Recently I migrated to next12 amplify config, and amplify realized an automated build of my main branch, but when I tried to log in, it says that my pool client does not exist but is showing an old deleted pool client id, I checked that my backend environment was pointing to the correct API and auth AWS apps, and it is, but when I visit my site, it still shows that my credentials are not valid because my pool client does not exist. I need to figure out how to revert or change to which environment my frontend points.

[ghost]

Hi @CLu1s 👋🏽 thanks for raising this issue. If your old user pool that has your credentials still exists, you can import that user pool via the Amplify CLI. Please follow our documentation for how to import that user pool:

• Unlink an existing Cognito User Pool or Identity Pool
• Import an existing Cognito User Pool

[github-actions[bot]]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.