Amplify .config project-config.json does not exist

[EtienneBauscher]

How did you install the Amplify CLI?

npm

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

v20.1.0

Amplify CLI Version

12.2.3

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.

Under the App Settings I have updated the Build settings to the below

Describe the bug

I get an error in the build phase on Amplify stating the below
2023-08-27T09:12:40.115Z [WARNING]: ✖ There was an error initializing your environment. 2023-08-27T09:12:40.119Z [INFO]: 🛑 Failed to pull the backend.

Also when I run amplify pull with the relevant appId and environment name I get the following error PATH/react/amplify/.config/project-config.json' does not exist

There is an instruction to include the Session Identifier which is 88a1397b-ec00-43c3-9db3-9a79cc0e13e1

Expected behavior

Expected behaviour is for the back end to deploy successfully on Amplify and the hostlink to display the updates made to the App.js file

Reproduction steps

Following the steps in section 'Set-up CI/CD of the frontend and back-end' of the tutorial https://aws.amazon.com/getting-started/hands-on/build-react-app-amplify-graphql/module-three/?e=gs2020&p=build-a-react-app-two

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.

[EtienneBauscher]

Okay so I resolved this issue by running amplify init in the terminal and setting up the project

[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.