Skip to content
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

User pool client vlr8k0on2pkuuotlbtqgg04la does not exist. #730

Closed
3 tasks done
anthony-dupont opened this issue Nov 21, 2022 · 11 comments
Closed
3 tasks done

User pool client vlr8k0on2pkuuotlbtqgg04la does not exist. #730

anthony-dupont opened this issue Nov 21, 2022 · 11 comments
Labels
login issues when logging into studio pending-response An issue is pending response from the issue requestor pending-triage An issue that is pending triage studio-backend An issue that needs to be tracked by Studio Backend team

Comments

@anthony-dupont
Copy link

Before opening, please confirm:

App Id

dx5nsgf78ravt

Region

eu-west-2

Environment name

any

Figma File Version (if applicable)

No response

Amplify CLI Version

No response

If applicable, what version of Node.js are you using?

No response

What operating system are you using?

No response

Browser type?

No response

Describe the bug

Not able to connect to amplify studio. Therefore we cannot amplify push/pull/ mock or anything.

Expected behavior

Amplify studio is logged in and we can use amplify push/pull

Reproduction steps

amplify push
pop window appear to connect to amplify studio

Project Identifier

No response

Additional information

No response

@johnpc
Copy link

johnpc commented Nov 23, 2022

I've noticed you've also commented on #721. Lets instead use this issue to discuss since the root cause appears to be different between these two issues.

@johnpc
Copy link

johnpc commented Nov 23, 2022

To unblock yourself, you can always reset your Studio authentication by disabling / re-enabling Studio in Amplify Studio settings in the AWS Amplify console.

@johnpc
Copy link

johnpc commented Nov 23, 2022

I saw you had permissions failures when you were first enabling Studio. This may have left your app in a half-enabled state that broke things. I understand how this happened and will add the fix to our backlog for prioritization. Unfortunately the only way to fix it now is to disable / re-enable studio as recommended above.

@johnpc johnpc added studio-backend An issue that needs to be tracked by Studio Backend team login issues when logging into studio pending-response An issue is pending response from the issue requestor and removed cli-login labels Nov 23, 2022
@anthony-dupont
Copy link
Author

Unfortunately I am not able to disable amplify Studio, I got an error message that the userPoolId does not exist.
User pool eu-west-2_OFlRDOXDO does not exist.
Very strange thing is that we started to create a new app and the same error appeared with the same user pool client...
Enabling Studio was done 6 months ago, so why now it would start failing because missing permission?

@github-actions github-actions bot removed the pending-response An issue is pending response from the issue requestor label Nov 24, 2022
@johnpc
Copy link

johnpc commented Nov 30, 2022

This user pool issue can happen when there is a failure disabling Amplify Studio - basically the "disable Amplify Studio" action partially succeeds before it fails, leaving the app in the state that you describe. There is a known bug here that you may have encountered that is causing this. We are working on the fix.

@johnpc johnpc added the pending-response An issue is pending response from the issue requestor label Nov 30, 2022
@ykethan ykethan added the pending-triage An issue that is pending triage label Nov 30, 2022
@ykethan
Copy link
Contributor

ykethan commented Dec 21, 2022

Hey, the fix has been published. Could you try disabling Amplify studio and re-enable the Studio application.

@ykethan
Copy link
Contributor

ykethan commented Jan 4, 2023

Closing the issue due to inactivity. If you are experiencing this issue, please feel in reopening this issue or open a new issue and link this.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2023
@CloudInnovator
Copy link

@ykethan Has this issue been fixed? I am facing the same problem today. I didn't have the same problem yesterday. The fix didn't seem to work

@yonirosenbaum
Copy link

Same Im having this issue still

@yonirosenbaum
Copy link

seems that it started happening on its own

@CloudInnovator
Copy link

CloudInnovator commented Mar 31, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
login issues when logging into studio pending-response An issue is pending response from the issue requestor pending-triage An issue that is pending triage studio-backend An issue that needs to be tracked by Studio Backend team
Projects
None yet
Development

No branches or pull requests

6 participants