if we

signOut()

then login again, the behavior of the

sIRTFrontend

cookie doesn't seem right. to reproduce: 1. Login 2. Signout 3. Login again from what we've observed, when

1

happens, the

sIRTFrontend

cookie gets set. Upon doing

2

the cookie gets set to

remove

. However when doing

3

, the

sIRTFrontend

value remains as

remove

then when performing

isAuthenticated()

, it always returns

false

because `sIRTFrontend`'s value is

remove

even though we have the access and refresh token cookies from the successful login. Seems like the culprit is here: https://github.com/supertokens/supertokens-website/blob/85e9f69bb7a17b6f807e5a1e457fc9163463a6e3/lib/ts/fetch.ts#L599 when the session has been created, I think

sIRTFrontend

should be set again. That, or remove that cookie as well during

signOut()

🤷‍♂️ we're currently getting away with the issue by doing the latter, which is to remove the

sIRTFrontend

cookie manually as well after

signOut()

. are we doing something wrong somehow?