Redirecting to authentication dialog - “An error occurred. Please try again later”

Question

Why does it always happen to me?

This happens after my application verify for user user login and redirect user to the authentication page:

https://w

Answer 1

I had tried all the answers mentioned here. But it didn't work. I had to delete and create again. I am guessing it was due to new the "Authenticated Referral". If you have added Open Graph objects which are not approved, it might give you an error.

Answer 2

I had the same problem and the root cause was different:

I was logged in as a Test User of a different application. Therefore I wasn't able to authorize an app that's not the one where the Test User was created for.

When I logged out and logged in as a regular user or a Test User for the app I tried to authorize, everything was OK.

Answer 3

I had the same problem after changing the domain of my site. Altough I properly changed the request_uri parameter and updated my app settings with the new domain, the error kept showing up. Then I realized that the ID and the SECRET ID of my Facebook APP had automatically changed with no warning!! The whole thing started working again using the new ID.

Answer 4

According to OAUTH Dialog documentation:

*redirect_uri: The URL to redirect to after the user clicks a button in the dialog. The URL you specify must be a URL of with the same Base Domain as specified in your app's settings, a Canvas URL of the form https://apps.facebook.com/YOUR_APP_NAMESPACE ...*

I am constructing oauth links dynamically to ask a user for additional permissions if needed and I realized, that even if you are redirecting to https://apps.facebook.com/YOUR_APP_NAMESPACE you have to have the App Domain and Website settings set in your application administration. I set domain to facebook.com and Website to facebooks root url.

Now my oauth dialog link works fine - even in sandbox mode.

Answer 5

Solution for me is to set option 'Authenticated Referrals' to enabled. Its realy fixed after that.

Answer 6

The issue resolved after I updated the 'appID' and 'secret' and then pushed the change back to heroku (i.e. - 'git push heroku master')

The key is not to forget to push the changes back to heroku master. Very easy to overlook if you're use to testing on localhost.

Hope this helps.