Hi, just a question about sessions in react native...
# support-questions-legacyb
binouse
09/15/2022, 9:04 AMHi, just a question about sessions in react native, should .signout() method delete the session ? Because it is not the case on my implementation and it is a bit of a problem as I am use .doesSessionExist() to determine if the user is signedIn or not
r
rp_st
09/15/2022, 9:10 AMhey @binouse yes it should delete the session. @nkshah2 can help here.
n
nkshah2
09/15/2022, 9:13 AMHi,
Just so I understand the situation, you are saying
doesSessionExistSuperTokens.signOutb
binouse
09/15/2022, 9:14 AMAbsolutely
n
nkshah2
09/15/2022, 9:14 AMCan I see the code for calling signOut?
b
binouse
09/15/2022, 9:17 AM Copy code
javascript
useSignOut: (): (() => Promise<void>) => {
const auth = useAuth();
const client = useApolloClient();
return async () => {
await client.clearStore();
try {
await Supertokens.signOut();
} catch (error) {
console.log("supertokens signOut error: ", error);
}
await AsyncStorageHelper.writeString(keys.authToken, "");
await AsyncStorageHelper.removeData("onboarding");
auth.setIsSignedIn(false);
};
},n
nkshah2
09/15/2022, 9:20 AMAre you using fetch when signing in?
nkshah2
09/15/2022, 9:20 AMor axios
b
binouse
09/15/2022, 9:20 AMYes fetch
n
nkshah2
09/15/2022, 9:21 AMCan I see the code for where you use
useSignOutb
binouse
09/15/2022, 9:24 AM Copy code
javascript
const signOut = AuthUtils.useSignOut();
const handleSignOut = async () => {
if (deviceToken) {
await deleteDeviceMutation({ variables: { token: deviceToken } });
}
await signOutMutation();
await signOut();
userLogOut();
};r
rp_st
09/15/2022, 9:24 AMand when do you call doesSessionExist?
rp_st
09/15/2022, 9:25 AMcan you call it right after doing
await signOut();b
binouse
09/15/2022, 9:27 AMalso true just after
await signOut();r
rp_st
09/15/2022, 9:27 AMhmm.
rp_st
09/15/2022, 9:28 AMCan you print out the value of
await Supertokens.doesSesionExist()await Supertokens.signOut();useSignOutb
binouse
09/15/2022, 9:29 AMLOG Session after signout: truebinouse
09/15/2022, 9:30 AM Copy code
javascript
try {
await Supertokens.signOut();
console.log("Session after signout: ", await Supertokens.doesSessionExist());
} catch (error) {
console.log("supertokens signOut error: ", error);
}n
nkshah2
09/15/2022, 9:31 AMb
binouse
09/15/2022, 9:34 AMAh, i reinstalled it and the doesSessionExist got true after my google sign in but stayed true at Supertokens.signOut()
binouse
09/15/2022, 9:38 AMHow can i catch the response from my API ?
n
nkshah2
09/15/2022, 9:39 AMMight be easier to debug this on call, ill send you a link
nkshah2
09/15/2022, 9:39 AMb
binouse
09/15/2022, 12:15 PMI changed my token handling process and it is working like a charm now
binouse
09/15/2022, 12:15 PMThanks a lot for your time and your help
binouse
09/15/2022, 12:15 PMYou guys are really amazing
n
nkshah2
09/15/2022, 12:15 PMGlad you got it working!
nkshah2
09/15/2022, 12:15 PMAnd yep, happy to help
r
rp_st
09/15/2022, 2:08 PMFor reference of anyone reading this in the future. The problem was that another token was being used for session management (other than supertokens session tokens) which was written to react native storage such that it replaced the cookies stored by supertokens.
rp_st
09/15/2022, 2:09 PMThis cause the sign out api to fail in session verification which makes it give a 200 reply, but it doesn’t clear cookies in this case.
rp_st
09/15/2022, 2:10 PMCause it didn’t clear access token cookies in this case, the other tokens (idRefreshToken) wasn’t cleared making doesSessionExist return true.
5 Views