Hi, I asked a while ago how I can implement Supertokens in an Ionic app. I was then referred to the page "Localstorage instead of cookies" (https://supertokens.com/docs/emailpassword/advanced-customizations/examples/localstorage/about), which also helped me a lot. Now, after a while, the access token expires and has to be refreshed. Supertokens also makes the Api call "refresh" automatically and it seems to work, but the Api endpoint still responds with ``401 try to refresh token``. This leads to an endless loop. If I now restart the page within the Ionic app, everything works again and the api always returns a 200 from now on, until the time when the access token expires again. I don't understand why this is happening. I manually set the header entry st-cookie in the app and the BackEnd reads this and overwrites the cookie entry. Am I doing something wrong? Thx

hey @beagle

Hi. So the fact that a restart fixes it points to it not being re-read for some reason

Yes, great, no stress at all, thank you very much 🙂

An ionic specific one? I think that'd be awesome.

well then I'll do that

I'll let @rp answer this (although it's getting late in his TZ), but I think it's looking good. It combines a few things (nestjs+gql+ionic) into a single example but I don't think that's an issue; it actually showcases a few things we don't have an example for.

As long as it works standalone and is easy to install and run with a clear readme, it would work well for us. I would suggest that you make the folder name “with-ionic” into something more specific like “with-ionic-nestjs-graphql”

ok thanks for the feedback. The "easy to start" could possibly be a small problem. Of course, in order to launch the Ionic app, an environment must first be created on the computer that allows an Android/Ios app to be started.

Oh yea. I mean as long as someone has all of that setup. Whatever is expected by ionic to work.