Parse invalid session token (Code: 209, Version: 1.7.1)

Question

I have just update both my Parse and Facebook SDK's (1.7.1 and 4.0 respectively) - both were an absolute pain to get working I might add!

However I now getting 209 errors when I try to log in with Facebook.

Here's an example of my code:

- (void)loginWithFacebook:(HMSuccessBlock)completion{
NSArray *permissionsArray = @[@"user_about_me",@"user_location",@"user_friends",@"user_relationships"];

// Login PFUser using Facebook

[PFFacebookUtils logInInBackgroundWithReadPermissions:permissionsArray block:^(PFUser *user, NSError *error) {
    if (!user) {
        NSLog(@"Uh oh. The user cancelled the Facebook login.");
        UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Log In Error"
                                                        message:error.localizedDescription
                                                       delegate:nil
                                              cancelButtonTitle:nil
                                              otherButtonTitles:@"Dismiss", nil];
        [alert show];
        completion(NO, error);

    } else if (user.isNew) {
        NSLog(@"User signed up and logged in through Facebook!");
        if (completion) {
            completion(YES, nil);
        }
    } else {
        NSLog(@"User logged in through Facebook!");
           completion(YES, nil);
    }
}];
}

Which yeilds the following [Error]: invalid session token (Code: 209, Version: 1.7.1)

My initial thinking is that the issue is something to do with my code in the app delegate - on older versions of the facebooksdk I would apply the following code

- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url sourceApplication:(NSString *)sourceApplication annotation:(id)annotation {
return [FBAppCall handleOpenURL:url
              sourceApplication:sourceApplication
                    withSession:[PFFacebookUtils session]];
}

However I cant seem to find anything to replicate this in the updated version, hence my code being

- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url sourceApplication:(NSString *)sourceApplication annotation:(id)annotation {
return [[FBSDKApplicationDelegate sharedInstance] application:application
                                                      openURL:url
                                            sourceApplication:sourceApplication
                                                   annotation:annotation];
}

Any help would be greatly appreciated.

This is now an accepted bug by Facebook Parse Eng team https://developers.facebook.com/bugs/756392341145634/ — CPD, Apr 29 '15 at 15:42

score 33 · Answer 1 · edited Dec 16 '15 at 02:04

33

Delete the app from the simulator or your phone, then rebuild and re-run the app. Sometimes an old token gets cached. I just solved this problem for my app.

edited Dec 16 '15 at 02:04

Don Alejandro

885
1
7
16

answered Apr 24 '15 at 20:53

TheRealRonDez

2,807
2
30
40

6

This solved my problem, but then reoccured again later – user499846 Jun 12 '15 at 09:16
Saved me. @user499846 you could have deleted data from the Parse db. That's probably the issue and that's definitely what caused my issue. – Lukesivi Nov 28 '15 at 12:40
If it's a hybrid app you can clear the session token by removing it from localstorage – James Parsons May 05 '16 at 00:05

score 18 · Answer 2 · answered Apr 14 '15 at 14:51

18

Check out this page: https://parse.com/tutorials/session-migration-tutorial

Most likely your app was using legacy session tokens. You can migrate to revocable session tokens by adding this to your app delegate right after you set the app id and client key.

    [PFUser enableRevocableSessionInBackground];

Parse's website has a section on handling this error that might be of more help to you: https://www.parse.com/docs/ios_guide#sessions-handleerror/iOS

answered Apr 14 '15 at 14:51

Mohssen Fathi

181
2

1

I had the same issue. When this happens, it won't allow you to make ANY calls to parse until the user is logged in. You have to disable Revocable Accounts and then call ParseUser.LoginAsync(username, pass); After I logged in, I removed the code and it could make calls to parse before the user is logged in again. – Levi Fuller Aug 02 '15 at 01:52
This worked for me --> PFUser.enableRevocableSessionInBackground() – Jay Dec 30 '16 at 01:14

score 7 · Accepted Answer · answered Jun 12 '15 at 09:19

7

Some of the answers posted were temporary fixes - however the problem could reoccur later if a user logged out and tried to log back in again - I think this was due to me allowing anonymous users also - the only way I could clear it is to call [pfuser logout] prior to log in

answered Jun 12 '15 at 09:19

user499846

681
3
11
24

That will cause the anonymous user to lose all of their data when the create an account, right? – picciano Jun 25 '15 at 23:37

score 2 · Answer 4 · edited Feb 18 '17 at 11:00

2

I think there some more steps need to be followed:

You have to add [FBSDKAppEvents activateApp] in applicationDidBecomeActive.
You should write
return [[FBSDKApplicationDelegate sharedInstance] application:application didFinishLaunchingWithOptions:launchOptions]; in method didFinishLaunchingWithOptions in AppDelegate.

Trying above steps should work for you.

edited Feb 18 '17 at 11:00

Reinhard Männer

14,022
5
54
116

answered May 01 '15 at 11:07

R_Developer

864
1
7
10

score 1 · Answer 5 · answered Jul 12 '19 at 14:17

With revocable sessions, your current session token could become invalid if its corresponding Session object is deleted from the Parse Cloud. This could happen if you implement a Session Manager UI that lets users log out of other devices, or if you manually delete the session via Cloud Code, REST API, or Data Browser. Sessions could also be deleted due to automatic expiration (if configured in app settings). When a device’s session token no longer corresponds to a Session object on the Parse Cloud, all API requests from that device will fail with “Error 209: invalid session token”.

Parse invalid session token (Code: 209, Version: 1.7.1)

5 Answers5

Linked