03/13/2013 – Updated post.
The Instagram API issue has been fixed.
The Instagram people left a comment on the forum thread explaining the problem.
We started appending an empty hash parameter to our URLs, to avoid hash-parameters leaking across an Instagram authorization flow.
Unfortunately, not all URL parsing libraries properly parse this out of request parameters, so we’ve started accepting codes either with or without the #_ at the end. Also, we’ve now added a whole separate parameter to separate the code from the hash, so the callback now looks like:
It seems like some apps are still having issues even with this fix, so we’re going to do the following: we’ll remove the empty hash for the next 3 weeks, and then re-enable it, to give folks times to update apps in the App Store etc. Just a reminder that it’s not enough to just read the code= and then everything afterwards; you should use whatever built-in URL parsing library for your platform to just parse out the code parameter.
We just got a tweet today from someone saying they were not able to set up their Instagram account in Blogsy. We tested it and we are also having the same problem. What we found is that there is currently a problem in the Instagram API. We have tweeted Instagram, sent an email and also commented on forum threads about this.
We have found that other developers are having the same problem with the Instagram API.
We are stilling waiting for someone from Instagram to respond about this issue. When I have more information to share I will update this blog post.