Facebook iOS SDK 3.1 is implemented in my app, and yet I’ve been using SSO, for the sake that it was easier to understand.
Now I am implementing the portions of the Facebook SDK that support iOS 6 Facebook account integration.
I’d like to know what’s anyone’s first thoughts about the problem after seeing this process:
On the simulator
sign into my facebook account in Settings app
switch back to my app
sign in with facebook account
handler for openActiveSessionWithReadPermissions gets state FBSessionStateOpen
everything works.
switch back to settings app
remove my account
sign in with facebook test user account
switch back to my app
sign in with facebook account
handler for openActiveSessionWithReadPermissions gets state FBSessionStateClosedLoginFailed
Before implementing the portion of Facebook SDK for iOS 6 integration, the Single-Sign-On worked perfectly, 100% of the time for the facebook test user account.
Is there any reason the iOS 6 integration will fail 100% on specific users where the SSO implementation works 100% for the same users?
Another final note: where my app appears in the list in Settings > Facebook, it is turned on/enabled.
I experienced the same issue. The core seems to be the fact that when you have FB credentials in the settings app, Facebook uses one route to authenticate. When you remove it, FB checks against the stored settings and fails and returns a close-state. It was expecting to be able to use the session but that was destroyed.
Keep in mind in a real-world setting, your user is not going to be toggling between the setup that way. It is very disconcerting when you are testing various scenarios on your device, but a real-world user is not going to attempt different user logins or different user-credential on/off scenarios.