I'm using FBSDKLoginKit to login with Facebook. I'm trying to get email, name, public profile and user profile link. According to latest policy to get profile link, developer need to ask permission during login and should provide how the information are being used to Facebook for review. I did all those process.
I was able to get all those required parameters when login with my developer Facebook account using FBSDKLoginManager. But when I tried login with another user account, profile link was declined in response. The link was empty.
I've created a method as below to login and get those parameters.
- (void)loginFaceBook
{
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
login.loginBehavior = FBSDKLoginBehaviorSystemAccount;
// need permission
[login logInWithReadPermissions:#[#"public_profile", #"email", #"user_link"]
fromViewController:self
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error)
{
if (error)
{
NSLog(#"Process error");
}
else if (result.isCancelled)
{
NSLog(#"Cancelled");
}
else
{
NSLog(#"Logged in");
if ([result.grantedPermissions containsObject:#"email"])
{
NSDictionary *params = #{#"fields" : #"id,name,link,email"};
[[[FBSDKGraphRequest alloc] initWithGraphPath:#"me" parameters:params]
startWithCompletionHandler:^(FBSDKGraphRequestConnection *connection, id responseData, NSError *error)
{
NSLog(#"%#",responseData);
if (!error)
{
NSString *fbEmail = [AQCommon validateTextBeforePack:[responseData objectForKey:kEmail]];
NSString *fblink = [AQCommon validateTextBeforePack:[responseData objectForKey:#"link"]];
NSString *fbname = [AQCommon validateTextBeforePack:[responseData objectForKey:#"name"]];
}
else
{
NSLog(#"Facebook login failed. Please try later."); }
}
}];
}
else
{
NSLog(#"Facebook login failed. Please try later."); }
}
}];
}
I got all the required parameters login with my Facebook developer account (where I've created my app), but user_link was declined for some other accounts. What could be the problem? Is it related to Facebook privacy policy? Or, user needs to change some settings in their profile?
Apart from the above problem, the profile link that I got of my developer account was opening from any Facebook account except some accounts. The error says either the link is expired or permission is not granted. The problem is very specific to Facebook user accounts. What could be the reasons and solutions?
Facebook provides sandboxed test users which can use be used for testing purposes.
Here you can check all about Facebook test users.
https://developers.facebook.com/docs/apps/test-users
It seems that facebook allow to see the profile only if the user is friend or friend of friend.
Is it possible to determine if the access freshly granted for my app?
I mean : I would like to be able to differentiate between
- a login that is made by a user who already granted access for my app earlier
and
- a login that is made by a user who just granted access for my app for the first time ever
Is it possible?
Thanks!
Check out https://developers.facebook.com/docs/facebook-login/ios/permissions/
if ([[FBSDKAccessToken currentAccessToken] hasGranted:#"publish_actions"]) {
// TODO: publish content.
} else {
FBSDKLoginManager *loginManager = [[FBSDKLoginManager alloc] init];
[loginManager logInWithPublishPermissions:#[#"publish_actions"]
fromViewController:self
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error) {
//TODO: process error or result.
}];
}
Since the release of the new FBSDK I'm facing this problem.
Scenario:
1.User logs into my app via FBLogin
2.User declines one of my permissions
My app sets him back to first screen (I don't allow creating an account without providing info)
He tries logging in again
He realizes FBSDK saved his settings he cannot change.
How do I provide the user with the possibility to change it?
My app runs to the point, I am noticing a declined permission and I give my user a notification to change the setting.
But I am clueless what to do at this point.
Firstly, you must not make all permissions as mandatory from Facebook.
Although if needed be, then you can check for the permission granted or not using the following code
if ([[FBSDKAccessToken currentAccessToken] hasGranted:#"publish_actions"]) {
// TODO: publish content.
} else {
FBSDKLoginManager *loginManager = [[FBSDKLoginManager alloc] init];
[loginManager logInWithPublishPermissions:#[#"publish_actions"]
fromViewController:self
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error) {
//TODO: process error or result.
}];
}
To check for Declined Permissions
FBSDKLoginManager *loginManager = [[FBSDKLoginManager alloc] init];
[loginManager logInWithPublishPermissions:#[#"publish_actions"]
fromViewController:self
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error) {
if ([result.declinedPermissions containsObject:#”publish_actions”]) {
// TODO: do not request permissions again immediately. Consider providing a NUX
// describing why the app want this permission.
} else {
// ...
}
}];
Note : If the user declines permissions, you should not immediately ask for them again. Instead your app should continue functioning. You may consider providing a guide or user interface explaining the benefits of granting that permission but should only ask for it again if the user performs an action that needs it.
Ref :
https://developers.facebook.com/docs/facebook-login/ios/permissions
https://developers.facebook.com/docs/ios/errors
I am using FB SDK v4.4 (latest) and think I have avoided the gotchas in the other questions.
I am establishing a logIn:
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
[login logInWithReadPermissions:#[#"email"]
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error) {
if (error) {
// Process error
} else {
[self facebookGetUserProfileWithCompletion:completion];
}
}];
I've specifically asked for "email" (an extended permission that requires app review).
My app has passed review, and the user gives permission for email when prompted. Adding a [result.grantedPermissions containsObject:#"email"] check in the handler returns TRUE.
Once the user's has responded to the UI, the code then gets the user profile from Graph API:
[[[FBSDKGraphRequest alloc] initWithGraphPath:#"me" parameters:#{#"fields" : #"id,email,first_name,last_name,link,locale"}]
startWithCompletionHandler:^(FBSDKGraphRequestConnection *connection, id result, NSError *error) {
if (!error) {
NSString *email = [result objectForKey:#"email"] ;
NSString *first_name = [result objectForKey:#"first_name"] ;
//etc...
}
At this point, I have just five parameters; I am missing email. Using Graph API Explorer, I get the full six. The user does have an email address registered with FB.
Why no email???!!!
I've pretty much resolved my issues. Here they are:
1) #cbroe had the most helpful suggestion of getting the token and using Graph API Explorer to debug. Lots of help there.
2) FB are shifting their DOB field to age_range in most cases. It seems that my existing app will still return DOB, but the new version will not without permission. No doc on this I could find, but if I go with age_range, I'm good.
3) There was a strange problem with my email address in my FB test account. That's fixed, and I am getting email again no problem. Again, the Graph API test was most helpful in resolving this. Thanks again #cbroe!
Your parameters should be just one string
#"fields:id,email,first_name,last_name,link,locale"
I've just updated facebook sdk v4.0
and according the tutorial of Using Custom Login UIs
-(IBAction)facebookLoginClick:(id)sender {
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
[login logInWithReadPermissions:#[#"email"] handler:^(FBSDKLoginManagerLoginResult *result, NSError *error) {
if (error) {
// Process error
} else if (result.isCancelled) {
// Handle cancellations
} else {
// If you ask for multiple permissions at once, you
// should check if specific permissions missing
if ([result.grantedPermissions containsObject:#"email"]) {
// Do work
}
}
}];
}
BUT the result is always nil and error code is 304, am I missing something?
I had a similar problem.
After initialising FBSDKLoginManager I added a line to flush out the data and the (Facebook)Token:
FBSDKLoginManager *loginmanager= [[FBSDKLoginManager alloc]init];
[loginmanager logOut];
Thus, exactly as the OP asks, "am I missing something"?
Yes, the following standard example code which is seen everywhere, is simply wrong:
-(IBAction)facebookLoginClick:(id)sender
{
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
---- ONE MAGIC LINE OF CODE IS MISSING HERE ----
[login logInWithReadPermissions:#[#"email"]
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error)
{
if (error) {...}
else if (result.isCancelled) {...}
else { // (NB for multiple permissions, check every one)
if ([result.grantedPermissions containsObject:#"email"])
{ NSLog(#"%#",result.token); }
}
}];
}
you must do this:
-(IBAction)facebookLoginClick:(id)sender
{
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
[login logOut]; //ESSENTIAL LINE OF CODE
[login logInWithReadPermissions:#[#"email"]
handler:^(FBSDKLoginManagerLoginResult *result, NSError *error)
{
if (error) {...}
else if (result.isCancelled) {...}
else { // (NB for multiple permissions, check every one)
if ([result.grantedPermissions containsObject:#"email"])
{ NSLog(#"%#",result.token); }
}
}];
}
Otherwise, very simply, the app will not work if the user happens to change FB accounts on the device. (Unless they happen to for some reason re-install the app!)
Once again - the popular sample code above simply does not work (the app goes in to an endless loop) if a user happens to change FB accounts. The logOut call must be made.
This happened to me when I changed the Facebook AppID (in the Info.plist file) switching form a test Facebook app to a production Facebook app. If your app sends the Facebook token to a server that generate a JWT for for instance, Facebook SDK still persists the fbToken (FBSDKAccessToken.currentAccessToken()) persisted unless it's told to remove it.
That may also happen in production when a user logs out of the app, a log out API request will log the user out and reset your JWT. But even before sending the log out API request, the client will need to tell the FBSDKLoginManager instance to log out.
if let currentAccessToken = FBSDKAccessToken.currentAccessToken() where currentAccessToken.appID != FBSDKSettings.appID()
{
loginManager.logOut()
}
I had this, it occurred when changing the FB app details in Xcode while an iOS app was running. You need to delete the app from the device and then republish with the new FB app setup. Just recompiling is not enough to clear the old FB settings
Swift 3.0
func loginWithFacebook
{
let loginManager = FBSDKLoginManager()
if let currentAccessToken = FBSDKAccessToken.current(), currentAccessToken.appID != FBSDKSettings.appID()
{
loginManager.logOut()
}
loginManager.logIn(withReadPermissions: ["public_profile","email"], from: self, handler: { (result, error) in
if error != nil {
print("error\(String(describing: error))")
}
else if (result?.isCancelled)! {
}
else {
print(FBSDKAccessToken.current())
}
})
}
You can use the following code to solve your problem :
[FBSDKAccessToken refreshCurrentAccessToken:^(FBSDKGraphRequestConnection *connection, id result, NSError *error){}
swift 4.0, 4.2, 5.0
FBSDKLoginManager().logOut()
According to the docs, 304 FBSDKLoginUserMismatchErrorCode "Indicates a failure to request new permissions because the user has changed".
Make sense in the scenario #Adrian999 mentioned.
Swift 4.0 and FBSDKCoreKit 4.33
let loginManager = LoginManager()
if let currentAccessToken = AccessToken.current, currentAccessToken.appId != SDKSettings.appId
{
loginManager.logOut()
}
Actually, the reason is very simple, you can try following step to reappear this error code easily.
The "Facebook login fail" may have two reasons:
you get the user info from facebook fail.
you get the user info from facebook success,but upload to your own server fail.
The code in FBSDKLoginManager.m is:
- (void)validateReauthentication:(FBSDKAccessToken *)currentToken withResult:(FBSDKLoginManagerLoginResult *)loginResult
{
FBSDKGraphRequest *requestMe = [[FBSDKGraphRequest alloc] initWithGraphPath:#"me"
parameters:nil
tokenString:loginResult.token.tokenString
HTTPMethod:nil
flags:FBSDKGraphRequestFlagDoNotInvalidateTokenOnError | FBSDKGraphRequestFlagDisableErrorRecovery];
[requestMe startWithCompletionHandler:^(FBSDKGraphRequestConnection *connection, id result, NSError *error) {
NSString *actualID = result[#"id"];
if ([currentToken.userID isEqualToString:actualID]) {
[FBSDKAccessToken setCurrentAccessToken:loginResult.token];
[self invokeHandler:loginResult error:nil];
} else {
NSMutableDictionary *userInfo = [NSMutableDictionary dictionary];
[FBSDKInternalUtility dictionary:userInfo setObject:error forKey:NSUnderlyingErrorKey];
NSError *resultError = [NSError errorWithDomain:FBSDKLoginErrorDomain
code:FBSDKLoginUserMismatchErrorCode
userInfo:userInfo];
[self invokeHandler:nil error:resultError];
}
}];
}
when currentToken.userID is not equal actualID, the FBSDKLoginUserMismatchErrorCode will throw.
Now, this issue will reappear when user A login facebook fail,but you do not have [FacebookSDKManager logOut] after the fail, the app will cache the accessToken for the user A , and then user A change facebook account to user B, when user B login facebook again,it will reappear this issue.
I was also stuck on this issue for a while. then i created object for FBSDKLoginManager in .h file and in viewDidLoad of .m file , initialize it and set logout property.
_fbLogin= [[FBSDKLoginManager alloc]init];
[_fbLogin logOut];
This helped me and hope helps you as well.
All the best.
Thanks
Single Sign On
I've also found that this issue happens if you have an app that does not require single sign on (i.e. an app which multiple users will create content and share from one device).
You can change single sign on in your app settings https://developers.facebook.com/apps/your-app-id/settings/.
For me in Objective-C following worked
FBSDKLoginManager *login = [[FBSDKLoginManager alloc] init];
if ([FBSDKAccessToken currentAccessToken]) {
[login logOut];
}
and issue was user was trying to login as another user as suggested by #Vineeth Joseph
Check the state of your FBSession:
isOpen
Indicates whether the session is open and ready for use.
#property (readonly) BOOL isOpen;
Declared In: FBSession.h
https://developers.facebook.com/docs/reference/ios/3.0/class/FBSession/
304 indicates that nothing has changed. Probably you are somehow already authenticated and so getting nil with 304 indicating nothing has changed.