Live data from Hacker News

Ask HN: Does anyone else have problems with Instagram API OAuth2?

news.ycombinator.com

51–60 of 82 posts

Re: Ask HN: Does anyone else have problems with Instagram API OAuth2?

#52

To temporary fix the issue, you could do the following: change response_type=code to response_type=token. Instagram will redirect back to your site with something like /callback#access_token=123456. From here, send the user to a very simple page with the following snippet: if (window.location.hash && window.location.hash.indexOf('#access_token=') !== -1) { var accessToken = window.location.hash.replace('#access_token…

Anyone have any experience getting this working with omniauth? It seems like one ought to just be able to change the config to:

    provider :instagram, ENV['INSTAGRAM_CLIENT_ID'], ENV['INSTAGRAM_CLIENT_SECRET'],  response_type: 'token'
But that doesn't seem to be working

Re: Ask HN: Does anyone else have problems with Instagram API OAuth2?

#55

We started having same issue since last Friday (Dec. 15, 2016) after working fine for months. Same user can login via oauth on one wifi, but not on the other, or even on mobile cellular network. And even when it worked on that wifi at one point, it does not work at other times. We have not found a workaround to fix this, reported to Instagram 24 hours ago, waiting...I tried to login to my account on instagram.com fir…

Update: as of now, All of our accounts are magically working. I did asked my facebook friends to pass the issue's urgency to Instagram team.

Re: Ask HN: Does anyone else have problems with Instagram API OAuth2?

#57
post #49

I've started having the same issue yesterday as well, noticed few times before but it was happening 'sometimes', now it happens all the time. Only workaround is to switch to implicit oauth as @xmrcivicboix suggested

Instagram has fixed the issue, at least it appears to be the case to us.

Re: Ask HN: Does anyone else have problems with Instagram API OAuth2?

#58
post #21

I'm creator of https://picodash.com , I noticed the same issue about a week ago but did not get any complains from my customers, so debugged it for 8 hours until I found this (I know it will be hard to believe): I kept getting "Matching code was not found or was already used." when using thru my oauth python code which btw has been working for 6 years now. But when I used curl to do POST, it worked, when I tried Curl…

Instagram has fixed the issue, at least it appears to be the case to us.

Re: Ask HN: Does anyone else have problems with Instagram API OAuth2?

#59
We're experiencing the same issue here. Reports from multiple clients over the last few days. Surely enough checking the logs yields an invalid_credentials error.

Trouble is, we can't faithfully reproduce the issue from our network, but clients are reporting failures to authenticate every time they try!

Have contacted Instagram for an update. Anyone else still experiencing the issue?

Re: Ask HN: Does anyone else have problems with Instagram API OAuth2?

#60
post #49

I've started having the same issue yesterday as well, noticed few times before but it was happening 'sometimes', now it happens all the time. Only workaround is to switch to implicit oauth as @xmrcivicboix suggested

Instagram has fixed the issue, at least it appears to be the case to us.

Are you sure about that? We're still getting this error.
Post reply on HN