Amplify Console build issue

I have a build that deploys fine using the CLI but not with the Amplify Console. The build log reports that it Cannot find file './components/SurveyContainer' in './src'. The repo is currently private, but I can show more if necessary.

The response during the frontend build activity is:

# Starting phase: build
2019-02-19T05:14:34.755Z [INFO]: # Executing command: yarn run build
2019-02-19T05:14:34.922Z [INFO]: yarn run v1.13.0
2019-02-19T05:14:34.973Z [INFO]: $ react-scripts build
2019-02-19T05:14:36.211Z [INFO]: Creating an optimized production build...
2019-02-19T05:14:40.807Z [INFO]: Failed to compile.
2019-02-19T05:14:40.809Z [INFO]: ./src/App.jsx
Cannot find file './components/SurveyContainer' in './src'.
2019-02-19T05:14:40.832Z [WARNING]: error Command failed with exit code 1.
2019-02-19T05:14:40.834Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2019-02-19T05:14:40.838Z [ERROR]: !!! Build failed
2019-02-19T05:14:41.791Z [ERROR]: !!! Non-Zero Exit Code detected
2019-02-19T05:14:41.792Z [INFO]: # Starting Environment Caching...
2019-02-19T05:14:41.792Z [INFO]: Uploading environment cache artifact...
2019-02-19T05:14:41.905Z [INFO]: # Environment Caching completed
Terminating logging...

[funkfinger]

After a productive call with folks at Amazon, this has been resolved. The issue was with the case insensitive nature of OS X vs the case sensitive nature of the deployment environment. OS X was not updating the filename in git even though the file name was changed on the local OS X machine- OS X wasn’t seeing a filename change when just the case was changing.

The solution was to change the filename case at GitHub.com. Had this not been an option, I believe I would have needed to delete the file and re-create it with the correct filename case.

Thanks Amazon! I’m looking forward to using these tools.

[sokic4]

Ma mrs