Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

challenge required erro #42

Open
ysf-alkheteeb opened this issue Sep 19, 2018 · 11 comments
Open

challenge required erro #42

ysf-alkheteeb opened this issue Sep 19, 2018 · 11 comments

Comments

@ysf-alkheteeb
Copy link

Instagram authentication failed (challenge required erro)
TypeError: Cannot read property '1' of null
at C:\Program Files\nodejs\node_modules\npm\node_modules\instagram-nodejs-without-api\instagram.js:76:23
at
at process._tickCallback (internal/process/next_tick.js:189:7)

@janmarkuslanger
Copy link

janmarkuslanger commented Sep 23, 2018

Have the same issue here!

@yatsenkolesh
Copy link
Owner

Hello, guys. You are need to change account

@rodrigueslg
Copy link

I tried with three differents accounts and still getting the same error

@aeroxy
Copy link

aeroxy commented Dec 16, 2018

I also ran into this issue.

Instagram authentication failed (challenge required erro) from Instagram.auth('username', 'password')

@benkaiser
Copy link
Contributor

Looks like it's fixed in master but not pushed to NPM.
See commit: ff03cd2

@yatsenkolesh
Copy link
Owner

@benkaiser I will publish it with your commit.

@benkaiser
Copy link
Contributor

benkaiser commented Jan 2, 2019 via email

@benkaiser
Copy link
Contributor

Btw @yatsenkolesh it seems following the code snippet from the readme also throws for me on getting the list of followers for a user (I think Instagram deprecated the /query/ endpoint, and you have to use /graphql/query and it has a slightly different API.

I don't know if I have any time today, but I'll try and get around to submitting a PR for fixing that too.

@yatsenkolesh
Copy link
Owner

It’s will great !

@Hazantip
Copy link

Hazantip commented Jan 6, 2019

Looks like it's fixed in master but not pushed to NPM.
See commit: ff03cd2

@yatsenkolesh npm still 1.0.3

@yatsenkolesh
Copy link
Owner

@Hazantip sorry for the delay. I published 1.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants