Environment name is invalid.

[foobarnes]

How did you install the Amplify CLI?

No response

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

No response

Amplify CLI Version

12.2.3

What operating system are you using?

macOS 13.4 (22F66)

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

I cannot amplify env checkout [...] one of my environments.

:) > amplify env checkout jason
🛑 Environment name is invalid.
[...]

:) > amplify env list        

| Environments |
| ------------ |
| *dev         |
| prod         |
| jason        |

:) > amplify env remove jason
🛑 Environment name is invalid.
[...]

:) > amplify pull --appId {{AMPLIFY_APP_ID}}
🛑 Environment 'jason' not found.
[...]

I was able to "select" the jason env like so:

:) > amplify env add jason
Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile
✖ Initializing your environment: jason
✖ There was an error initializing your environment.
🛑 Could not initialize platform for 'jason': Missing required key 'Bucket' in params

:) > amplify env list        

| Environments |
| ------------ |
| dev          |
| prod         |
| *jason       |

:) > amplify status  
🛑 File at path: '[...]/amplify/#current-cloud-backend/amplify-meta.json' does not exist

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
[...]

Expected behavior

Expected to be able to check out

Reproduction steps

I'm not sure how I got myself into this mess 🤷‍♂️

Project Identifier

aae37be032a2f135dcdf89710fccdf92

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey @foobarnes, thank you reaching out. Do observe a missing jason block in your team-provider-info.json?
could you try running amplify pull --appId <app-id> --envName dev --yes to see if that pulls the environment?
if that does not work, you will need to remove the missing jason block from the local-aws-info.json and repull the environment.

Similar issue: #12887

[foobarnes]

Thanks, @ykethan, where is local-aws-info.json? I can't find it. I don't have a .config directory in my amplify directory.

[ykethan]

@foobarnes the file may be hidden in VSCode, in you project directory under .vscode -> settings.json. set the amplify/.config as false.

[foobarnes]

Amazing, thank you so much! I need to learn my VSCode better 🥲

Trying now.

[foobarnes]

That did it! You're awesome, @ykethan .

I'd recommend adding this helpful tip to the CLI Team Environments > Troubleshooting page since that's where I went to look for info about how to find my local-aws-info.json file. :)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[ykethan]

@foobarnes thank you for the feedback.