Mihály Lengyel

I couldn't reproduce it in tests. I think we should reduce the isolation level if the problem persists. I have two theories: 1. Something is wrong with the index. Something...

We've decided to leave this as-is for now. Leaving this issue open and we'll monitor if it pops up again.

This error doesn't happen inside `SuperTokens.init`, the request is likely started by either an "auth" component (e.g.: `EmailPasswordAuth`) or calling `doesSessionExist`. In my quick experiment, it seems to work correctly....

I checked it out, but I'm still not 100% sure about replicating your issue. One of the flows I tried: 1. Started core 2. Went to `app-one` (http://localhost:4001) 3. I...

I'm not sure how to replicate (and fix) this. Just to check: - what browser are you using (incl. version)? - are you in incognito mode? I'm happy to try...

Oh, sorry for the late response. This got a bit lost in my notifications. So everything seems to be in order; incognito could've caused issues. About screen sharing: if you...

We should definitely make changes to `supertokens-website` first when implementing, this PR is more about the interface we are planning.

1. I think we'd need to do this whatever API we provide. The requests should return an error (or throw) anyway; adding a helper function to get the id of...

1. Structure of missing claims returned by the backend: - We should clarify that the id is the id of the claim validator (and maybe rename the id of the...

We've postponed discussions of this, so I'm saving my notes here: - "We want to show a login feature component even though a session exists" - this has been solved...