Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 82 posts

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

#13

Post by navied »

AlexWhite_ wrote: post #4
svens_ wrote: post #2

Currently I'm seeing a lot of 400 errors: "Matching code was not found or was already used."

We at smartmetrics.co experience the same issue. We noticed that issue affected not everybody, many customers still can use oauth. We contacted Instagram and Facebook support but got no answer.

We are experience the same issue, I have been able to reproduce the issue with the same account by just trying it repeatedly. It will eventually fail, the only solution is to sign out of Instagram, which ends up clearing your session and trying it again.

Instagram had a long period of time it went down yesterday I'd be surprised if they aren't linked.

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

#14

Post by svens_ »

navied wrote: post #13
AlexWhite_ wrote: post #4

Earlier quoted context omitted.

We at smartmetrics.co experience the same issue. We noticed that issue affected not everybody, many customers still can use oauth. We contacted Instagram and Facebook support but got no answer.

We are experience the same issue, I have been able to reproduce the issue with the same account by just trying it repeatedly. It will eventually fail, the only solution is to sign out of Instagram, which ends up clearing your session and trying it again. Instagram had a long period of time it went down yesterday I'd be surprised if they aren't linked.

Private mode wasn't enough to fix the error for us.

At least not in all cases, i.e. we tried production, staging and an instance running on localhost. Private mode usually changed in which places the login worked, but it never helped for all three.

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

#15

Post by AlexWhite_ »

svens_ wrote: post #14
navied wrote: post #13

Earlier quoted context omitted.

We are experience the same issue, I have been able to reproduce the issue with the same account by just trying it repeatedly. It will eventually fail, the only solution is to sign out of Instagram, which ends up clearing your session and trying it again. Instagram had a long period of time it went down yesterday I'd be surprised if they aren't linked.

Private mode wasn't enough to fix the error for us. At least not in all cases, i.e. we tried production, staging and an instance running on localhost. Private mode usually changed in which places the login worked, but it never helped for all three.

Yep, it works not for all accounts.

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

#16

Post by maltloafdev »

svens_ wrote: post #2

Currently I'm seeing a lot of 400 errors: "Matching code was not found or was already used."

We're seeing the same issue, even when testing with a fresh sandboxed Instagram app. Originally thought it'd be down to an issue with Omniauth/Devise (the Ruby gems we are using).

1) send user to authorise at Instagram: GET https://www.instagram.com/oauth/authorize?client_id=XXX&redi... Instagram sends user to your redirect URL with: /?code=YYYY

2) post code to Instagram to exchange for access token: curl -F 'client_id=XXXX' \ -F 'client_secret=ZZZ' \ -F 'grant_type=authorization_code' \ -F 'redirect_uri=http://localhost:3500' \ -F 'code=YYYY' \ https://api.instagram.com/oauth/access_token

3) Instagram responds with: {"error_message": "Matching code was not found or was already used.", "code": 400, "error_type": "OAuthException"}

Post reply on HN