Project Path Error claims Directory Path does not exist

Describe the bug Backend build process is failing and the error references amplifi “featureFlags.js”. My project path exists and it is correct. This issue started about 4 days ago.

To Reproduce Steps to reproduce the behavior:

1. After updating the lambda function
2. Amplify push -y
3. Go to Amplify Console
4. See error in Build section.

Expected behavior The build should work correctly as it did before and the process will deploy the next version of the code.

Code Snippet This is the log from the Backend Build Process

Starting phase: build

Executing command: amplifyPush --simple

2020-07-27T19:38:17.079Z [INFO]: Project path: ‘C:\Users\myusername\Documents\Projects\projectname’ does not exist. 2020-07-27T19:38:17.080Z [INFO]: Error: Project path: ‘C:\Users\myusername\Documents\Projects\projectname’ does not exist. at Function.FeatureFlags.initialize (/root/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-cli-core/lib/feature-flags/featureFlags.js:246:15) 2020-07-27T19:38:17.085Z [ERROR]: !!! Build failed 2020-07-27T19:38:17.085Z [ERROR]: !!! Non-Zero Exit Code detected 2020-07-27T19:38:17.085Z [INFO]: # Starting environment caching… 2020-07-27T19:38:17.086Z [INFO]: # Environment caching completed Terminating logging…

Environment

npx envinfo --system --binaries --browsers --npmPackages --npmGlobalPackages

Binaries: Node: 12.18.1 - C:\Program Files\nodejs\node.EXE npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD Browsers: Chrome: 84.0.4147.89 Edge: Spartan (44.18362.449.0) Internet Explorer: 11.0.18362.1 npmPackages: @testing-library/jest-dom: ^4.2.4 => 4.2.4 @testing-library/react: ^9.5.0 => 9.5.0 @testing-library/user-event: ^7.2.1 => 7.2.1 aws-amplify: ^3.0.11 => 3.0.11 aws-amplify-react: ^4.1.10 => 4.1.10 bootstrap: ^4.5.0 => 4.5.0 bootstrap-switch-button-react: ^1.2.0 => 1.2.0 formik: ^2.1.4 => 2.1.4 react: ^16.13.1 => 16.13.1 react-bootstrap: ^1.0.1 => 1.0.1 react-datepicker: ^2.16.0 => 2.16.0 react-dom: ^16.13.1 => 16.13.1 react-icons: ^3.10.0 => 3.10.0 react-router-dom: ^5.2.0 => 5.2.0 react-scripts: 3.4.1 => 3.4.1 react-select: ^3.1.0 => 3.1.0 styled-components: ^5.1.1 => 5.1.1 yup: ^0.29.1 => 0.29.1 npmGlobalPackages: @aws-amplify/cli: 4.25.0

You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = ‘DEBUG’; in your app.

[fuhreeus]

@attilah Thanks. My .gitignore file is woefully inadequate and I will be updating it for the reasons you listed.

Now that I’m thinking back, I can say that I created my .gitignore file myself. Amplify did not auto-generate it.

I will try your workaround and report back.

[attilah]

@fuhreeus @AravindTReddy by default Amplify CLI generated .gitignore excludes the local-env-info.json file because it contains information about the locally initialized environment. Is there a particular reason why you have checked it into source control?

If you add the file back to .gitignore and remove it from source control, that could unblock you to use the latest version of the CLI, while we will work on a workaround.