I am developing at sveltekit/capacitor app... in android everything works ok with regrds to supertokens authentication... but in ios devices, I get a successfull sign-in with a success response from server, but then the once I try to authenticate using the

Session

I get:

No session exists

error. Any ideas?

Hi, there. I'm trying to implement Sign In with Google using the following instruction https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/thirdparty-login. But when I call

thirdPartySignInAndUp

after redirect it throws me error `Error: No instance of ThirdPartyEmailPassword found. Make sure to call the ThirdPartyEmailPassword.init method. `But, actually, it was successfully initialised as I was able to call getAuthorisationURLWithQueryParamsAndSetState to generate auth url. Any ideas what I'm doing wrong?

Hello, I'm using FastAPI and my goal is to implements by myself the route /auth/signup because I want it to be visible on the open-api swagger. Currently I don't have a front-end, so I'm only using the swagger. I'm struggling with get_session and create_new_session. After I log-in, get_session always returns None.

py
class UserRegisterModel(BaseModel):
    email: str
    password: str


@router.post('/register')
async def register_user(
    request: Request,
    user: UserRegisterModel,
):
    email_password_quertier = Querier.get_instance('emailpassword')
    path = NormalisedURLPath('/recipe/signup')
    response = await email_password_quertier.send_post_request(path, user.dict())
    if response.get('status') == 'OK':
        user_id = response['user']['id']
        session = await create_new_session(
            request,
            user_id
        )
        return True
    raise Exception('user exists')

@router.post('/like_comment') 
async def like_comment(request: Request):
    session = await get_session(request, session_required=False)

    if session is None:
        raise Exception("Should never come here")
    user_id = session.get_user_id()

    print(user_id)

Hey, I have a website and a chrome extension. What i want to do is when the user logins inside the website, he should automatically login inside the extension as well. This is a business project.

Is there a recommended way to implement a "remember this device" feature?

Hello I'm trying to implement a custom SMTP configuration for passwordless auth as specified in this guide https://supertokens.com/docs/passwordless/email-delivery/smtp/configure-smtp . The problem though is that the init method from passwordless does not expect any parameter such as

emailDelivery

as specified in the above-linked article. Could you please help take a look at this? Type - Supertoken NodeJS Version - 11.3.0

Anywhere that I could find a example of using Vanilla JS to create custom UI?

Hi team I'm running into a new CORS error we haven't had in the past. The CORS configuration is now blocking requests between our api (express) and client (react) with the error message: "Access to fetch at 'https://vms-api.macleanengineering.com/auth/signin' from origin 'https://vms.macleanengineering.com/' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled." We've set out cors configuration according to the user/password user guide so I'm starting here. Here's our current cours config: app.use(cors( { origin: ['https://vms.macleanengineering.com/'], allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], credentials: true, } ));

I discovered today that Playwright might give devs access to the browser's cookies. (Would have to confirm on my own.) If they do, it could be a great tool for testing example repositories since it also enables devs to disable JavaScript in the browser during end to end testing. If a set of standard test cases could be created, they could be run against any example repo to make sure everything still works as expected during repo NPM package upgrades, etc. Hoping to look into this sometime within the next 4 months. But sounds pretty exciting (since it would take away a lot of manual work).

Is it safe to set checkDatabase to false in verifySession for all endpoint if I am writing my own logic for checking revoked blacklisted tokens? What does supertokens core check apart from checking whether the token is blacklisted?