`amplify add env` creates new Amplify project and app ID

[josefaidt]

How did you install the Amplify CLI?

pnpm

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

18

Amplify CLI Version

10.5.1

What operating system are you using?

mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

n/a

Describe the bug

Creating a new environment with amplify add env creates a new Amplify project with a separate App ID.

Expected behavior

An environment is created in the existing project

Reproduction steps

1. amplify init -y
2. amplify add env --envName next --yes
3. observe new app id in amplify/team-provider-info.json

Project Identifier

No response

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.

[sagr4019]

@josefaidt is this also a bug in previous amplify-cli versions?
It would be great if we can specify the appId for the new environment

[TandyN]

I also have been able to reproduce the error when I selected the AWS Profile option when running the command amplify add env to add the env. This created a brand new app with a new app id.

I decided to try and add the env with the AWS access keys prompt instead by entering aws access key id & secret manually and this seemed to have been able to point to the same app I was currently checked out to with the Amplify CLI.

I'm currently using Amplify CLI Version 10.4.1

[ailen0ada]

I encountered the same issue in my environment.
I created an Amplify App in a different account by switch-rolling, and when I added an environment, a new AppId was generated.
After adding an IAM user and creating a separate profile for the access key and secret, a prompt appeared asking which AppId to associate with the new environment. This suggests that SSO or switch-rolling may need to be handled better.
I'm using version 12.5.1.

[powelli]

Also seeing this issue. Coupled with the fact that there's no way to query or confirm which AppId will be used until you actually init the environment, this was really frustrating and has resulted in several hours of confusion and lost productivity.

Currently using Amplify CLI version 13.0.0 but had experienced the same issue with 12.x before upgrading.

Worked around it after reading the comments above by selecting Amplify Studio as the authentication method instead of AWS profile but this is very counter-intuitive. For reference the AWS profile being used is assumed through SSO & role switching.

It was resulting in our shared development AWS account being littered with loads of extra Amplify projects/apps with unique AppIds instead of multiple envs (per developer) under a single AppId which is the way we've always organised them before.