question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`amplify init` always fails with `TypeError: Cannot read property 'Stacks' of null`

See original GitHub issue

Describe the bug When running amplify init it always throws TypeError: Cannot read property 'Stacks' of null with no clear way to proceed or fix it.

Amplify CLI Version 4.29.4

To Reproduce

  1. Create an empty directory.
  2. Run amplify init
  3. Select ios as the type of the app.

Expected behavior amplify init succeeds.

Screenshots Screenshot 2020-10-08 at 10 06 16

Desktop (please complete the following information):

  • OS: macOS 10.15.7 (19H2)
  • Node Version: v12.19.0

Additional context This error was preceeded by https://github.com/aws-amplify/amplify-cli/issues/5509, but that one is no longer an issue for me as I don’t attempt to start amplify with npx here.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:17 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
MaxDesiatovcommented, Oct 8, 2020

You don’t have to configure the Amplify CLI to assume a role, it can directly use a IAM user’s credential. But you could configure it to assume a role.

From the following error message, the profile that you’ve selected is from a role with source_profile set to a user that is NOT set up to assume a role. Open the <home-dir>/.aws/config file you can see the profiles.

Is this mentioned in the Amplify “Getting started” documentation anywhere? I’m following the steps exactly as they are specified in the documentation, so my assumption is that either documentation is up to date and all the steps will succeed as described in it, or errors will be shown that will direct me and clearly state what’s wrong and how to fix it.

If you follow the instruction from the document, you will be able to set it up.

Shouldn’t this document be directly linked from the “Getting started” and “Prerequisites” sections if following that document is required to get amplify init to work?

0reactions
dpalme3160commented, Jun 3, 2022

I’m having the same issue

Read more comments on GitHub >

github_iconTop Results From Across the Web

TypeError: Cannot read property 'projectPath' of undefined ...
As I am new to amplify I'm not sure it completely fixes any problem that was created, but it appears to allow me...
Read more >
Troubleshoot CloudFormation stack issues in AWS Amplify
When I try to deploy my AWS Amplify application, I receive an AWS CloudFormation error similar to the following: "Resource is not in...
Read more >
AWS-Amplify/Lobby - Gitter
in the console I get: Uncaught (in promise) TypeError: Cannot read property 'props' of undefined at t.value (ToolbarSelect.js:203). does anyone solve that?
Read more >
cannot read properties of undefined (reading 'auth') - You.com
Firebase App (the core Firebase SDK) is always required and must be listed first import firebase from "firebase/app"; // If you are using...
Read more >
How to prevent cannot read property split of undefined
The error "Cannot read property split of undefined" can occur when performing any of these types of operations if the variable is undefined....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found