603466164219281420 #support-questions

I have a question about the signOut() method listed under common customizations within the session recipe. This is a method from the supertokens-auth-react package to be called on the front end. When you say it revokes the session the on the front end and backend, does that mean someone who was implementing a react frontend would only need to invoke signOut once on the front end?

bill92

02/01/2022, 10:26 PM

Testing passwordless auth with SMS, I have an rq hook, for some reason it's not working if I don't include the

withCredentials

and set it to

true

. Is this expected?

Copy code

ts
import axios, { AxiosError } from "axios";
import { useQuery, UseQueryResult } from "react-query";
import { PatientResponse } from "../lib/types/patient";

const getPatients = async () => {
  const { data } = await axios.get<PatientResponse>(
    "http://localhost:5555/patient",
    {
      headers: {
        "Content-Type": "application/json",
      },
      withCredentials: true,
    }
  );
  return data;
};

export const useGetPatients = (): UseQueryResult<
  PatientResponse,
  AxiosError
> => {
  return useQuery(["patients"], getPatients);
};

bill92

02/01/2022, 10:26 PM

dummy hook!

02/02/2022, 3:49 AM

@gadi interesting.. can you open an issue about this on our GitHub and we can come up with a solution for it

02/02/2022, 3:50 AM

@workoutintheabstract yes. Calling it just once would work.

02/02/2022, 3:50 AM

@bill92 you need to add our interceptor to the imported axios instance.

bill92

02/02/2022, 4:00 AM

yes! I did had it but I was importing the incorrect instance 😵‍💫

02/02/2022, 4:01 AM

Ah okay. So now it’s fixed?

bill92

02/02/2022, 4:09 AM

yup 😅

bill92

02/02/2022, 4:10 AM

I do have a new issue when running ST core, I follows all the instructions, when I go to the test endpoint

http://localhost:3567/hello

, "Hello" is returned, but whenever I try to start passwordless auth I get the error on react that says,

Something went wrong. Please try again

02/02/2022, 4:14 AM

Hmmm. Can you add a generic error handler in your backend and print out the error there? What does it say?

bill92

02/02/2022, 4:15 AM

Error: No SuperTokens core available to query

bill92

02/02/2022, 4:22 AM

Copy code

Server ready
Error: No SuperTokens core available to query
    at Querier.<anonymous> (/Users/gmwill934/Documents/gmwill934/supertokens-otp/api/node_modules/supertokens-node/lib/build/querier.js:225:27)
    at Generator.next (<anonymous>)
    at /Users/gmwill934/Documents/gmwill934/supertokens-otp/api/node_modules/supertokens-node/lib/build/querier.js:30:75
    at new Promise (<anonymous>)
    at __awaiter (/Users/gmwill934/Documents/gmwill934/supertokens-otp/api/node_modules/supertokens-node/lib/build/querier.js:12:16)
    at Querier.sendRequestHelper (/Users/gmwill934/Documents/gmwill934/supertokens-otp/api/node_modules/supertokens-node/lib/build/querier.js:218:13)
    at Querier.<anonymous> (/Users/gmwill934/Documents/gmwill934/supertokens-otp/api/node_modules/supertokens-node/lib/build/querier.js:245:43)
    at Generator.throw (<anonymous>)
    at rejected (/Users/gmwill934/Documents/gmwill934/supertokens-otp/api/node_modules/supertokens-node/lib/build/querier.js:22:44)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

bill92

02/02/2022, 4:22 AM

more precise

02/02/2022, 4:22 AM

I see. Are you running the node process in a docker container?

bill92

02/02/2022, 4:22 AM

correct

bill92

02/02/2022, 4:22 AM

both postgres and st core

02/02/2022, 4:22 AM

Right. So if you pass localhost:3567 to that, it will point to inside the docker container and not localhost of the host machine

02/02/2022, 4:23 AM

so you might want to provide the local IP address of your machine instead of localhost

02/02/2022, 4:23 AM

Or configure a docker network and use those hostnames..

bill92

02/02/2022, 4:24 AM

okay, i'll use docker compose and set everything up

bill92

02/02/2022, 4:24 AM

😄

bill92

02/02/2022, 4:25 AM

thanks!

02/02/2022, 4:25 AM

You're welcome 🙂

bill92

02/02/2022, 5:18 AM

Still getting error, using in memory database docker-compose

Copy code

version: '3.9'

services:
  api:
    build: .
    ports:
      - '5555:5555'
    depends_on:
      - supertokens
  supertokens:
    image: registry.supertokens.io/supertokens/supertokens-postgresql

bill92

02/02/2022, 5:18 AM

a network is created by default and I'm able to resolve using the service name

02/02/2022, 5:18 AM

What is the connectionURI that you passed in the node process?

bill92

02/02/2022, 5:19 AM

Copy code

export const InitializeSupertokens = () =>
  SuperTokens.init({
    framework: 'express',
    supertokens: {
      connectionURI: 'supertokens:3567',
    },
    appInfo: {
      appName: 'tlantli',
      apiDomain: process.env.API_URL as string,
      websiteDomain: process.env.WEB_URL as string,
      apiBasePath: process.env.AUTH_PATH as string,
      websiteBasePath: process.env.AUTH_PATH as string,
    },
    recipeList: [
      Passwordless.init({
        flowType: 'USER_INPUT_CODE',
        contactMethod: 'PHONE',
        createAndSendCustomTextMessage: async (input) => {
          const { phoneNumber, userInputCode } = input;
          client.messages.create({
            body: userInputCode?.toString(),
            from: TWILIO_PHONE_NUMBER,
            to: phoneNumber,
          });
        },
      }),
      Session.init(),
    ],
  });

bill92

02/02/2022, 5:19 AM

supertokens

bill92

02/02/2022, 5:19 AM

that's what I passed