Bug with Instagram API Login - This page could not be loaded

Question

Since few days I have problems with the API instagram. Instagram sending this error page after the user has entered this login information.

"This page could not be loaded. If you have cookies disabled in your browser, or you are browsing in private mode"

Do you know why ? How to do ? Need help

Answer 1

On webapp authentication... the problem is related to instagram platform. I found that the problem arise only if your browser don't have the instagram cookie "ig_cb" set. This is set when you accept cookie policy on instagram.com. The workaround is to go on instagram and accept cookie policy then go back to your social auth and proceed.

This happens for both mobile and desktop users (browser).

Being a block on instagram login process... I guess there's no definitive solution other than wait for instagram bug fix.

Answer 2

I hate to be the bearer of bad news, but we also had this problem, which flagged on the Facebook Dev page: https://developers.facebook.com/support/bugs/406930029718049/

They have looked into the problem, as a number of us have had this exact issue too. It is only affecting EU user, as our US users are logging in and signing up without problems, and it seems that Facebook are refusing to look into it - their Instagram Platform API forum has already stopped accepting issues.

In terms of what we have learnt since last week, we think:

• It is likely GDPR related
  • Not all apps have been affected, Bumble does not have this problem but Tinder does
  • It is happening with both the old Platform API and Graph API, according to a developer who has already migrated to Graph.
  • No one seems to know anything!

UPDATE:

So it seem's it is in fact a cookie issue on mobile. When a user goes to sign in on mobile view, the 'accept cookie' message that typically appears on web doesn't appear. However, when the error screen pops up, if you click 'Log in' in the top right, it will redirect you to the web view, which lets you accept the new terms and conditions. Then, once you direct back to mobile the cookie seems to have been saved and you can now login. This has worked for us on iOS so far, but not Android, and we still haven't come up with a work-around yet.