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

Amplify CLI: AWS Amplify Failed to communicate with the Amplify CLI [using Brave & other Chromium based browser] #410

Closed
3 tasks done
zachjonesnoel opened this issue Dec 19, 2021 · 2 comments
Labels
bug An issue which has been identified as a bug

Comments

@zachjonesnoel
Copy link

Before opening, please confirm:

App Id

No response

Region

us-east-1

Environment name

staging

Amplify CLI Version

7.6.3

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

v16.13.0

What operating system are you using?

Windows

Browser type?

Brave and Edge (Chromium based) browsers

Describe the bug

Whenever I'm trying to configure Amplify for pulling the env from Amplify Studio, this error pops up when validating the authentication.

image

Expected behavior

Authentication being successful and then able to pull the details from env.

Reproduction steps

  • Use the command prompted by Amplify Studio to configure and then authenticate the user.
  • On click of verify yes as prompted on the browser, it shows the error message.

Additional information

Tried it first on Brave, then saw there is already an issue with it #278 so tried on Edge which is also a Chromium based browser and has the similar experience.

@busster
Copy link

busster commented Dec 21, 2021

Hello @zachjonesnoel, thank you for raising this issue to our attention. We are currently investigating and will make sure to update you when we have a solution.

@renebrandel renebrandel added bug An issue which has been identified as a bug cli-login labels May 27, 2022
@renebrandel
Copy link
Contributor

Hi folks - we just launched the new Amplify CLI version 9.1.0 to address this workflow! Check out all the details here: #84 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue which has been identified as a bug
Projects
None yet
Development

No branches or pull requests

3 participants