I keep seeing the confirm page at every login click about react-native-fbsdk HOT 8 CLOSED

This is by design, any time there's an app switch this dialog will show, regardless of whether the user has authorized the app already.

from react-native-fbsdk.

@mingflifb There is no plan to change this?

from react-native-fbsdk.

This is by design to increase user trust, since flashes of app switch back and forth with no explanation is a bad experience. If the user has explicitly logged out of your app, and logs in again, they will see this dialog. If the user is not logged out explicitly, we will cache the access token so you can use it across app starts. Is your app logging out the user when it shuts down, or is the user explicitly choosing to log out?

from react-native-fbsdk.

It makes sense now that you explained. Thanks for that. Just out of
curiosity, when you say "we will cache the access token", where exactly the
token is stored? In the server, cookies in browser? I know we can retrieve
user's token but from where we get it?

Thanks a lot for your quick response!

SM
On Sep 9, 2015 10:13 AM, "Ming Li" [email protected] wrote:

This is by design to increase user trust, since flashes of app switch back
and forth with no explanation is a bad experience. If the user has
explicitly logged out of your app, and logs in again, they will see this
dialog. If the user is not logged out explicitly, we will cache the access
token so you can use it across app starts. Is your app logging out the user
when it shuts down, or is the user explicitly choosing to log out?

—
Reply to this email directly or view it on GitHub
#28 (comment)
.

from react-native-fbsdk.

It's securely stored locally on the device.

from react-native-fbsdk.

@steveleec I use ParseReact to do my login and it has a ParseReact.currentUser that saved the Facebook user, you might want to check that out

from react-native-fbsdk.

@mingflifb how do we access that access token?

from react-native-fbsdk.

Use the FBSDKAccessToken

from react-native-fbsdk.