andy-HM

I am running into the same thing. @hanamurayuki did you have the `aws-exports.js` committed before you tried this? I have tried using `.easignore` and simply not including `aws-exports.js`. I have...

Any update on this? This just occurred to me as well when deploying to my production environment. Worked fine when deploying to my dev and test environments.