Confusing messaging leads to duplicate projects: "You are not working in a valid Amplify project"

[omenking]

In AWS Amplify, you can build a web application without having to ever pull the backend because you are using the Admin UI.

It is very easy to run into the error "You are not working in a valid Amplify project" and then be prompted to run amplify init

Then you will run amplify init and not realizing that it has now just created a second application.

A more clear message would be along the lines of:

We detected no local backed files suggesting there is no provisioned backend. 
This command requires a backend environment deployed to AWS and the presence of these backend files.
If you already have a backend environment within the AWS console you need to pull these files
If you have yet to create a backend environment you can run ampify init to initialize a new project that will provision a blackened environment to AWS

[renebrandel]

Hi @omenking good feedback. What do you think of this prompt:

No Amplify backend project files detected within this folder. Either initialize a new Amplify project or pull an existing project.
- "amplify init" to initialize a new Amplify project
- "amplify pull <app-id>" to pull your existing Amplify project. Find the <app-id> in the AWS Console or Amplify Admin UI.

[gitaalekhyapaul]

@yuth @renebrandel would an error like this work?

If yes, I would like to be assigned to this issue

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.