Kethan sai

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

Hey @floriankrueper, thank you for reaching out. I was able to reproduce the issue using the following reproduction steps. 1. `amplify add auth` and `amplify update auth` to add oauth...

Hey @R70YNS, thank you for reaching out. could you try running `amplify update auth`, select `Update OAuth social providers`, re-enter the credentials and run `amplify push`. This should update the...

Hey @R70YNS, could you provide us the project identifier by running `amplify diagnose --send-report`? > Remove authentication provider in AWS console noticed this, could provide us some information on how...

Hey @R70YNS, could you try the following 1. run `amplify update auth` -> `Update OAuth social providers`. deselect the providers. 2. remove the deployment secrets from `team-provider-info.json` 3. delete the...

@R70YNS thank you for the information. From the project identifier did not observe any reference in the `cli-inputs.json` or `backend-config.json` but noticed a reference in the `root-cloudformation-stack.json`. Do you observe...

Hey @R70YNS, would be open for a quick call wanted to dive into the project. I am available on discord and my handle is `ykethan`

Hey, 👋 thanks for raising this! Marking as feature-request. Unfortunately, you will need to script out the file creation and references in the `backend-config.json` and `team-provider-info.json` to automate the creation...

Hey @tchowdhury, Thanks for reaching out. Does this error also occur if you run the terminal with Admin access?

Hey @tchowdhury, could try setting the profile using AWS CLI `aws configure` or manually adding them. https://docs.aws.amazon.com/cli/latest/userguide/welcome-examples.html You should be to able to use the profile with admin permissions on...