I am using the supertokens middleware in our backend; and seeing this error. Is it something that I should handle? {"type":"SessionError","message":"Failed to verify access token","stack":"Error: Failed to verify access token at Object. (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:89:19) at Generator.next () at /usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:44:75 at new Promise () at __awaiter (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:26:16) at Object.getInfoFromAccessToken (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/accessToken.js:57:12) at Object. (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/sessionFunctions.js:105:55) at Generator.next () at fulfilled (/usr/src/app/node_modules/supertokens-node/lib/build/recipe/session/sessionFunctions.js:15:36) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)","errMagic":"ndskajfasndlfkj435234krjdsa","fromRecipe":"session","isBoom":true,"isServer":true,"data":null,"output":{"statusCode":500,"payload":{"status":500,"error":"Internal Server Error","message":"An internal server error occurred","code":"UNKNOWN","data":null},"headers":{}}},"msg":"Failed to verify access token"}

Is it causing a 500 error to be thrown from your api?

Yes its causing a 500 error to be thrown; we are using "supertokens-node": "^13.1.2" Our backend framework is hapi(nodejs) and we are using the verifySession() middleware

Right. Let me have a look

Yes; its not like always crashing So the scenario where it crashes is when the user is successfully logged in; it interacts well with our apis...all good Now he leaves the browser open and comes back after 2-3 hours(probably the token expired by then); so our api is called...which has verifySession middleware; which throws an error

ah yea i know

Yes yes; added using supertokens.init So all routes are working fine; including consumerOtp etc So no issue with the middleware I guess

So the middleware is supposed to catch this kind of error and send a 401 to the client.

This is my middleware code if it helps: supertokens.init({ framework: 'hapi', supertokens: { connectionURI: appConfig.game.supertoken.url, apiKey: 'our key', }, appInfo: { // learn more about this on https://supertokens.com/docs/session/appinfo appName: 'ESPNCricinfo Games', apiDomain: appConfig.global.baseUrl, websiteDomain: appConfig.global.webBaseUrl, apiBasePath: '/v1/game/auth', websiteBasePath: '/game/auth', }, recipeList: [ Passwordless.init({ flowType: 'USER_INPUT_CODE', contactMethod: 'PHONE', getCustomUserInputCode: (userContext): string => { return Math.floor(1000 + Math.random() * 9000).toString();//to generate 4 digit codes }, smsDelivery: { override: originalImplementation => { return { ...originalImplementation, sendSms: async input => { //my custom impl.. }, }; }, }, }), Session.init({ getTokenTransferMethod: () => 'header', }), ], });

have you done this step? https://supertokens.com/docs/passwordless/custom-ui/init/backend#3-add-the-supertokens-apis--cors-setup

Yes added the plugin

that's still ok

Let me verify the plugin thing

yes

You are awesome Hope that fixes things

can you try and see if this works?

Sure, need to replicate the scenario in my local and then fix I have another prod issue to fix before that Shall I confirm this to you by 8pm?

yea sure.

It worked @rp_st If it repeats, then will let you know

Great