You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
Firstly, this is such a sweet framework. Really easily integrated and removes much hassle. Great job!
I've been seeing an issue with Facebook Login. I've created a FB developer account and created the iOS section to receive the appID, which then is used in the AppDelegate didFinishLaunchingWithOptions SimpleAuth.configuration[@"facebook"] = @{ @"app_id" : @"ABC"};
Everything actually works fine, but there are some occasions where certain devices encounter this issue:
The work around I use at the current moment is to request user to sign into FB within the Settings itself. To make it clear, I requested the user facing this issue to navigate to Settings -> Facebook -> Sign In if not already, check to see if the switch for the app under Facebook section is turned on.
Question is, why is this needed for certain users? Is there a workaround for this issue?
Thanks a lot!
The text was updated successfully, but these errors were encountered:
The facebook provider requires that the user is signed in to Facebook on their device, and that your app has access to their account. How would it work otherwise?
You are free to use facebook-web instead, which means users will have to log in to their Facebook accounts every time they want to authorize. That's a pretty poor user experience.
Either way, the issue you are describing is not related to anything in Settings > Facebook. You are getting a 400 Bad Request back from Facebook which means your app has access to their system Facebook account and has gone on to the network authorization step.
If you were getting a 401 Unauthorized it would mean that the device's Facebook tokens have expired.
Unfortunately, I do not have additional info regarding this issue. As you have pointed out since it's a 400 Bad request issue instead of the Settings issue. I was just curious because certain devices was having this issue, and when user enable the FB login via Settings it works fine. Probably it was a whole other issue all together. My bad.
Thanks again!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
Firstly, this is such a sweet framework. Really easily integrated and removes much hassle. Great job!
I've been seeing an issue with Facebook Login. I've created a FB developer account and created the iOS section to receive the appID, which then is used in the AppDelegate didFinishLaunchingWithOptions SimpleAuth.configuration[@"facebook"] = @{ @"app_id" : @"ABC"};
Everything actually works fine, but there are some occasions where certain devices encounter this issue:
The work around I use at the current moment is to request user to sign into FB within the Settings itself. To make it clear, I requested the user facing this issue to navigate to Settings -> Facebook -> Sign In if not already, check to see if the switch for the app under Facebook section is turned on.
Question is, why is this needed for certain users? Is there a workaround for this issue?
Thanks a lot!
The text was updated successfully, but these errors were encountered: