I have run into another weird issue. Trying to sign in from a mobile device (Android, using latest Chrome). Sign in fails with:

t (in promise) TypeError: Failed to fetch
    at recipeImplementation.js:171:58
    at Function.<anonymous> (fetch.js:562:46)
    at g (fetch.js:136:31)
    at Object.next (fetch.js:73:24)
    at h (fetch.js:29:36)
(anonymous) @ recipeImplementation.js:171
(anonymous) @ fetch.js:562
g @ fetch.js:136
(anonymous) @ fetch.js:73
h @ fetch.js:29
await in h (async)
dt @ react-dom.development.js:4164
sf @ react-dom.development.js:4213
ff @ react-dom.development.js:4277
th @ react-dom.development.js:4291
Fv @ react-dom.development.js:9041
xO @ react-dom.development.js:9073
Hy @ react-dom.development.js:9086
jv @ react-dom.development.js:9097
(anonymous) @ react-dom.development.js:9288
CP @ react-dom.development.js:26140
JS @ react-dom.development.js:3991
zy @ react-dom.development.js:9287
Lw @ react-dom.development.js:6465
Av @ react-dom.development.js:6457
pC @ react-dom.development.js:6430

Hi, cookie based auth is not working on desktop Safari, is that expected?

Hi, can anyone tell me how to verify the JWT token?

Hey!!! There is a table named `userid_mapping `in the supertokens core's database (when we are using self-hosted service). Could this table be used to map the user ids from supertokens database with some external NoSQL database, say MongoDB, which our application uses? Also, is there any table that can store additional session information that our application fetches?

I'm logged out after using supertokens with multiple api endpoints ( https://supertokens.com/docs/passwordless/common-customizations/sessions/multiple-api-endpoints)

Hello again I would like to translate the emails that supertokens sends to our customers. I understand that I can change the content as described here: https://supertokens.com/docs/emailpassword/email-delivery/smtp/change-email-content But how do I know into which language I have to translate? I would be happy to get the language that users saw as they register in the browser.

java
Error: Initialisation not done. Did you forget to call the SuperTokens.init function?

I keep getting this error when going to my /testauth path but I did call the function before the route

import { verifySession } from "supertokens-node/recipe/session/framework/express/index.js";

router.get("/testauth", verifySession(), (req, res) => {
  if (req.session == null) {
    res.send({ error: "Must be signed in", code: "401" })
    return
  }
  let userId = req.session.getUserId();
});

Is it possible to integrate SuperTokens with an encore.dev app? In general, encore.dev lets you build (in, honestly, the very best possible way) a set of lambda-type functions (which you can deploy pretty much anywhere). You specify just the function, and in a comment the URL that will be matched to that function at run-time. You really don't have to set up anything else, it's fantastic, and they deploy it. So I'm not talking about the ST core, but just the ST server routes -- is it possible to have ST "hook into" the encore.dev routing somehow? I'll ask on their slack channel as well. Thanks!

how can I check authentication in swagger? because we are using cookies-based authentication.

Hi, I tried running supertokens (the binary) in aws lambda and it doesn't seem to work. What I did was I downloaded the supertokens-postgresql binary, dockerize it by copying the binary over to the docker image and installing it there. I tried to "docker ps" into it and ran "supertokens start" and it worked. However, when I deploy the image to AWS lambda it fails to run everytime. Hence, I set the erro flag in config.yaml to "null" so that the error would show in std-in, and what I found was always a java exception, something related to read-only file system. I suspect this is because aws lambda has the entire file system as read-only, except for /tmp. But Supertokens is trying to write to /usr/lib/supertoken/webserver-temp. Any idea about this? I essentially tried to run "supertokens start" when the lambda function is triggered but failed to do so.