Cli: Heroku Login Error: Cannot read property 'body' of undefined

[RakelO]

Trying to login using to heroku using heroku cli with command heroku login

Getting error:

TypeError: Cannot read property 'body' of undefined
    at new HerokuAPIError (/usr/local/lib/node_modules/heroku/node_modules/@heroku-cli/command/lib/api_client.js:12:33)
    at Login.login (/usr/local/lib/node_modules/heroku/node_modules/@heroku-cli/command/lib/login.js:78:19)
    at <anonymous>

I'm using MacOs 10.12

[jdxcode]

We're under a code freeze right now but this is likely an issue with npm installs. You'll need to use the standalone in the meantime

[jdxcode]

Because npm doesn't use the yarn lockfile there is some mismatch between transitive dependencies (I'm pretty sure at least)

[rmcfall17]

I am getting a similar error message on the standalone

[rmcfall17]

try typing this your terminal:
wget -qO- https://toolbelt.heroku.com/install.sh | sh
then login:
heroku login

I had a very similar error message and this solved the problem.

[wilharlley]

I have the same error:

(.venv) wilharlley@wilharlley:~/i9amazon/i9gestao$ wget -qO- https://toolbelt.heroku.com/install.sh | sh
This script requires superuser access.
You will be prompted for your password by sudo.
[sudo] senha para wilharlley:

• [[ ! :/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin: == :/usr/local/bin: ]]
  ++ uname
• '[' Linux == Darwin ']'
  +++ uname -s
  ++ expr substr Linux 1 5
• '[' Linux == Linux ']'
• OS=linux
  ++ uname -m
• ARCH=x86_64
• '[' x86_64 == x86_64 ']'
• ARCH=x64
• mkdir -p /usr/local/lib
• cd /usr/local/lib
• rm -rf heroku
• rm -rf /home/wilharlley/.local/share/heroku/client
• curl https://cli-assets.heroku.com/heroku-linux-x64.tar.xz
• tar xJ
  % Total % Received % Xferd Average Speed Time Time Time Current
  Dload Upload Total Spent Left Speed
  100 16.0M 100 16.0M 0 0 216k 0 0:01:15 0:01:15 --:--:-- 185k
• rm -f /usr/local/bin/heroku
• ln -s /usr/local/lib/heroku/bin/heroku /usr/local/bin/heroku
• '[' -f /usr/local/heroku/bin/heroku ']'
  heroku installed to /usr/local/bin/heroku
  heroku/7.0.86 linux-x64 node-v10.1.0
  (.venv) wilharlley@wilharlley:~/i9amazon/i9gestao$ heroku login
  heroku: Enter your login credentials
  Email [[email protected]]: TypeError: Cannot read property 'body' of undefined
  at new HerokuAPIError (/snap/heroku/2936/node_modules/@heroku-cli/command/lib/api_client.js:12:33)
  at Login.login (/snap/heroku/2936/node_modules/@heroku-cli/command/lib/login.js:78:19)

[AndreaPontrandolfo]

I'm having the same error. Windows 7 here.

[elreydetoda]

for linux only (i.e. cloud9, centos, ubuntu) - https://github.com/heroku/cli/issues/881#issuecomment-395196160

[wilharlley]

My friend @jdxcode , I'm new to git and I'm trying to understand how to proceed so I can have my calls resolved. The 881 call, which opened and returned, was not resolved. I posted the contents of the terminal after running the script to try to help walk the solution. You have deleted it and would like to know if you are still working on the problem, or I have to look for other sources.
Please, I need an orientation on how to proceed.
Sorry, my english, I'm from Brazil.

[jdxcode]

We're aware of this issue. This issue is already tracking it. You keep posting the same information and that is not helpful. We're all at a company-wide conference this week so our availability is very spotty. This is our top priority right now though and as soon as I have some time I will resolve the issue.

[wilharlley]

@jdxcode
Now I understand. Excuse. Evolving, always. Thanks for the feedback.

[johnvross]

Just FYI I am having the same problem when I try to 'heroku login'. I have completely removed node and npm.

[Marciodm]

I am facing the same problem in windows 10.

`heroku login
heroku: Enter your login credentials
Email: [email protected]: Cannot read property 'body' of undefined
at new HerokuAPIError (C:/Program Files/heroku/client/node_modules/@heroku- 
cli/command/lib/api_client.js:12:33)`
at Login.login (C:/Program Files/heroku/client/node_modules/@heroku- 
cli/command/lib/login.js:78:19)`

[johnvross]

Marciodm I was able to resolve my issue by typing my email in a text editor, copying it to my clipboard, and then pasting it quickly before the error came up. That enabled me to login. I am on Windows 10 as well, using bash on windows.

[Marciodm]

Thank you @johnvross !
For now I'll use your tip. I hope they'll sort it out soon enough.

[AndreaPontrandolfo]

Marciodm I was able to resolve my issue by typing my email in a text editor, copying it to my clipboard, and then pasting it quickly before the error came up. That enabled me to login. I am on Windows 10 as well, using bash on windows.

This worked, thank you!

[jdxcode]

I wasn't able to reproduce this at all. I did ship a beta just now though that forces some of the dependencies to be updated which I think may have been causing this.

Can someone try running heroku update beta to see if this fixes the issue? You'll need to be on an updatable version of the CLI for this to work. Run curl https://cli-assets.heroku.com/install.sh | sh to install standalone.

[Marciodm]

Hello @jdxcode !
I just ran, but the error is now another.

´C:\Users\Marcio
λ heroku update beta
heroku: Updating CLI from 7.0.87 to 7.0.87-beta.5da7c01 (beta)... done
heroku: Updating CLI... done

´C:\Users\Marcio
λ heroku login
heroku: Enter your login credentials
Email: ######@gmailError: invalid error
    at new HerokuAPIError (C:/Users/Marcio/AppData/Local/heroku/client/7.0.87- 
beta.5da7c01/node_modules/@heroku-cli/command/lib/api_client.js:13:19)
    at Login.login (C:/Users/Marcio/AppData/Local/heroku/client/7.0.87- 
beta.5da7c01/node_modules/@heroku-cli/command/lib/login.js:78:19)´

[jdxcode]

OK I figured it out, the latest update (7.0.88) should work now. The issue was because we added a prompt timeout feature but did not have it disabled by default.

[Marciodm]

Hello @jdxcode !
It's working perfectly now.
Thank you very much for the support.

[foxenn]

@johnvross thank you, worked