amplify-cli: Amplify commands has TypeError preventing schema change

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the Amplify Console GitHub Issue Tracker

Describe the bug I am using Amplify with a React Native Project. I am realizing that I am not able to use Amplify commands on the CLI without an error:

TypeError: Cannot read property 'forEach' of undefined
    at AmplifyToolkit.showHelpfulProviderLinks [as _showHelpfulProviderLinks] (/usr/local/lib/node_modules/@aws-amplify/cli/lib/extensions/amplify-helpers/show-helpful-provider-links.js:12:15)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.exports.run (/usr/local/lib/node_modules/@aws-amplify/cli/lib/commands/status.js:6:5)
    at async Object.executeAmplifyCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/index.js:173:9)
    at async executePluginModuleCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:153:5)
    at async Object.executeCommand (/usr/local/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
    at async Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/lib/index.js:82:9)

Amplify CLI Version 4.32.1

To Reproduce Amplify status or Amplify push

Expected behavior Amplify status will work, but show the error. Amplify push will fail because of this error.

Desktop (please complete the following information):

  • OS: Mac
  • Node Version: v12.18.4

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (8 by maintainers)

Most upvoted comments

@jhockett yup once I got that folder back I was able to use amplify pull --restore and everything works fine now.

@jhockett Unfortunately I lost that information.

However,

Please accept my apologies – I removed my comment from above: the problem seems to have disappeared for me – I just rebuilt the entire project (9 resources) from scratch (amplify delete, amplify init, …) and now everything is working perfectly fine.