I am migrating our Auth0 Facebook connection to a new app. The connection against the new app was working until recently. Now when I try to perform a Facebook login or test the connection whilst using the new app the below error is returned
If I revert the connection back to use the old Facebook app credentials the connection and logins work fine.
If anyone has experienced this before I’d be keen to hear from you. Otherwise I may need to try creating another Facebook app from scratch and see if that makes a difference.
A small update, I did try creating a Facebook app from scratch but after attempting the connection test from Connections → Social I receive the same error.
I noticed however between the app which works and the new app which does not there is a different API version being used.
Trying to test the connection against the new app which uses v8 returns this error
{
"error": "invalid_request",
"error_description": "(#100) Tried accessing nonexisting field (viewer_can_send_gift) on node type (User)"
}
I’m afraid to toggle our working app over to v8 if we can’t then downgrade it back. It’d be nice to try this just to confirm the API version discrepancy is contributing to the behaviour.
We’re in the same boat as @jamesdbxt (our existing app using v6.0 works, but our newly created app using v8.0 does not work)
We had an old unused app lying around using v6.0 of Facebook Login. Repurposing that app and creating a new Facebook connection in Auth0 did not work either and results in the same error.
EDIT: I turns out our Facebook app was somehow upgraded to 8.0 without our knowledge. You can disregard the previous statement about v6.0 producing the same error.
Quick Update: Able to replicate the issue on my side as well. We have informed our engineering team on this with complete details.They will be working on to resolve the issue, will let you know once I get a further update
Any general details about time to fix? We are getting ready to launch a new consumer facing site, and would prefer to launch with Facebook login enabled, but if it is looking more like a week rather than a day to fix, it would be good to know, as we will launch with Facebook disabled.
@sidharth.chaudhary any updates on when this will be fixed? It is hard to imagine that there is not more attention on this considering one of the biggest social providers on Auth0 is currently broken for v8.0 apps.
Facebook will not allow us to downgrade our app to v6.0 since it was created with v8.0.
For anyone looking for a work-around we successfully re-purposed an older Facebook app ID with Graph API v7.0 for use with Auth0.
If you have an older Facebook app (< v8.0) that is used in a test, qa or staging environment it might be an option for you to re-purpose it for an Auth0 connection that is affected by this issue.
Keep in mind that switching away from your re-purposed Facebook app at a later point could be problematic depending on your use of Auth0.
Also, older Facebook apps that are not in use will most likely require re-activation of Graph API access and will force you to upgrade it to v8.0 so a candidate Facebook app is one that has somewhat recent usage.
We’re in the same boat, don’t have access to an older FB API version app, and will have to launch our product this week without FB auth. Not good, considering it was one of the key Auth0 selling points
Any updates on this ? We are considering Auth0 as our solution, but seeing that something as major as this ( Facebook being one of the main social logins ) is not resolved for 11 days… definitely makes us rethink whether Auth0 is the right choice.
Any workaround for someone who doesn’t have any previous version FB app would be highly appreciated
