Thanks, Rob.
By the way, logout DOES work on Android and Kindle, so this is an iOS-only problem, as it was before.
It may be the team is using close instead of closeAndClearTokenInformation in iOS.
Jorge
I understand that Engineering fixed something today, but because they don’t have an app that fails, they can only guess if it worked. If this does not fix it for you, you will need to submit a sample app that has the issue along with the steps to reproduce it…
Please let know if this works. It should have been a plugin change, so no need to update Corona SDK.
Rob
Hi Rob, I can confirm that logout now works on iOS! 
Thank you for the quick turnaround!
Jorge
I can confirm that the bug is fixed Trying to login after a logout will now take me to facebook again instead of using the same session.
Hi Rob, the logout functionality seems to be broken again. Same problem as before.
Facebook has recently changed their API I wonder if this is causing the problem.
I noticed that build CoronaSDK 2014.2319 mentions that a logout issue has been fixed, but it hasn’t fixed the issue in my case.
I have only tested this in iOS, not sure if Android is also affected.
Can you be a little more specific about the problem? I need something more than “Its broken” to take to engineering, especially if they just fixed it.
Rob
Sure, Rob!
In my app, I have a button to login to Facebook and another button to Logout.
Before, I was able to switch users in my app by doing this:
1- I would login to Facebook via a the Facebook app (or by going to Facebook.com if I don’t have the app installed)
2- I would launch my game and click on the “Log in to Facebook” button.
3- My app would grab my current Facebook user and I would be able to see my avatar, list of friends, etc within my app.
4- I would then click my Logout button, which uses facebook.logout()
5- I would go to the Facebook app (or Facebook.com) and I would switch to different user.
6- Then I would return to my app and click on the “Log in to Facebook” button again.
7- My app would then grab the NEW user from Facebook and show me this user’s avatar and list of friends.
What is happening now, is that no matter what I do, my app will not grab the new user info, it will keep on login me in with the user I first signed up with. Basically, it is not erasing the Facebook token/cache.
This is exactly the same issue that I reported in January 7th.
It may be that the Corona team is again not using closeAndClearTokenInformation or it may be that the changes on the Facebook API have changed how logout works.
Jorge
I can confirm the same issue Jorge is having. The login persists after calling logout. 
This could be a change from Facebook. They now try to use the iOS builtin login information when possible (I think). Let me ask engineering.
Thanks, Rob.
By the way, logout DOES work on Android and Kindle, so this is an iOS-only problem, as it was before.
It may be the team is using close instead of closeAndClearTokenInformation in iOS.
Jorge
I understand that Engineering fixed something today, but because they don’t have an app that fails, they can only guess if it worked. If this does not fix it for you, you will need to submit a sample app that has the issue along with the steps to reproduce it…
Please let know if this works. It should have been a plugin change, so no need to update Corona SDK.
Rob
Hi Rob, I can confirm that logout now works on iOS!
Thank you for the quick turnaround!
Jorge
I can confirm that the bug is fixed Trying to login after a logout will now take me to facebook again instead of using the same session.
Hi all.
I’m using version 2014.2393. I tested on android device with facebook apps installed.
I cant logout from corona apps (status was ‘logout’, but the token seem persisted. login after logout didnt ask user email and password), unless i logout from facebook apps.
But the logout success when the device has no facebook apps. (had to reenter email and password after corona’s logout)
Anyone got the same issue? Is this the way it works?
To Jorge: did you get something like this before? or now?
To ArdentKid: have you tested on android? I didnt try on IOS myself…
Thanks before.
That’s how it is meant to work if the user is logged in to their account on the official FB app, it’s supposed to simplify the process, if I recall correctly. (May want to refer to FB docs for more detailed explanation of the process.)
Answer by Peach Pellen,
I’ve found today that I’m getting almost the same problem. The first time I connect Facebook, allow the permissions and save the facebook token in local, then, remove (unlink) the app on the Facebook applications, then I restart and call the graph api of facebook to know if the token is already available. It returns an error (of course : token is no more available), then I call the facebook.login() function and it returns me a success login, but the returned token is the previous one, before I’ve unlinked the app.
The thing is that if I call after that the facebook.logout() function, it erases the cached token, and then I call again the facebook.login() it will works like the first time.
I would like a function that I could call even if I’m not connected, to erase the cached token.
Is it possible?
Hi all.
I’m using version 2014.2393. I tested on android device with facebook apps installed.
I cant logout from corona apps (status was ‘logout’, but the token seem persisted. login after logout didnt ask user email and password), unless i logout from facebook apps.
But the logout success when the device has no facebook apps. (had to reenter email and password after corona’s logout)
Anyone got the same issue? Is this the way it works?
To Jorge: did you get something like this before? or now?
To ArdentKid: have you tested on android? I didnt try on IOS myself…
Thanks before.
That’s how it is meant to work if the user is logged in to their account on the official FB app, it’s supposed to simplify the process, if I recall correctly. (May want to refer to FB docs for more detailed explanation of the process.)
Answer by Peach Pellen,
I’ve found today that I’m getting almost the same problem. The first time I connect Facebook, allow the permissions and save the facebook token in local, then, remove (unlink) the app on the Facebook applications, then I restart and call the graph api of facebook to know if the token is already available. It returns an error (of course : token is no more available), then I call the facebook.login() function and it returns me a success login, but the returned token is the previous one, before I’ve unlinked the app.
The thing is that if I call after that the facebook.logout() function, it erases the cached token, and then I call again the facebook.login() it will works like the first time.
I would like a function that I could call even if I’m not connected, to erase the cached token.
Is it possible?