UnleashedMind

This might be related to an issue https://github.com/jprichardson/node-fs-extra/issues/577 are you using node version 10.x? We haven't tested the cli on node version 10. x

We are investigating this issue. Please provide the following information - node version - awsmobile-cli version - open your project's awsmobilejs/#current-backend-info/backend-details.json file, look for `AWS::Lambda::Function`, see if there is an...

Is it that for every `AWS::Lambda::Function` there's a `configHandlerName` attribute? Or if there's one `AWS::Lambda::Function` that's missing the `configHandlerName` attribute?

Thanks for the feedbacks, I will mark this as feature request, we'll keep improving our products.

Yes, by executing the init command with the project id of the Mobile Hub project that you wanted to switch to. `awsmobile init ` you can find the mobile hub...

This is a server side issue, we've identified the cause for multiple versions of zip files been uploaded, the server side team has been notified, we will inform you on...

We are investigating this issue. This happens at the last step of the pull, the cli is updating the backend (your development) contents with the latest. So the contents in...

What is your cli and node version? I was not able to reproduce this error, with the same symlink in the node_modules/.bin folder.

the cli only works for node version 7+, so node version 6.* is not a good choice. Could you please try to use node version 8.9.0? That's the version that's...

Thanks for the feedbacks @SeanBannister What you guys are doing is correct in terms of how collaborations on a project should be done using awsmobile-cli. For the newly added appsync...