You need to override the sign up API. So in the override object, instead of passing “functions”, you should pass “apis”

And in that, you will find signUpPOST function which you can override. And in that, you will have access to input.options.req

Thanks @User !!!

@User Also one thing to keep in mind is that Apple credentials are tied to bundle identifiers for iOS devices. And the demo app uses a specific library to make it work. If you are testing on an iOS device/simulator and getting the error the bundle ID may be the problem. Also any additional info would help: What OS you are trying it on? Did you use the same library for Apple auth that the demo app does? Did you see an error on the Apple sign in view (that the device renders on iOS or the webpage on Android) or is it a specific API thats throwing it etc etc

Hello,i have another question about localization if possible, Does switching between languages work for you guys, because mine is just showing English language

How are you switching between languages?

You need to call the i18next lib for that since you are using that

Just using the URL

Hmm. Is that how you are supposed to switch langugues in i18n? I'm not sure.

using router with locale = ""

I see.

hi

Changing language from i18n file works perfect

I tested it with just i18n and calling changeLanguage

but when i use next router

nothing changed at auth level. but the application still load the french language

Yes @User

so is supertokens inside the router that has the locale setting? I'll have to look into this, but my guess is that's where the context is set up.

or do you have a repo I could look at? I think that'd be the easiest.

unfortunately I'm working on private repo with more complications haha

hmm, ok. so how are you embedding supertokens? is it inside the route where the locale is set?

Well the configuration was made before i start working on it, what I did is to split login / register / reset password into three different pages since i'm working on nextjs project, and integrate localization

will share with you how's my structure

@User i did implement i18next.changeLanguage but still the component does not rerender

Implement

changeLanguage

? You mean an event handler? Could you call the

i18next.changeLanguage

manually to test if it actually changes the language of the auth UI? e.g, in the browser console?

Hi @User , How are you? I am trying to debug a bug that we faced in our environments. We have 2 environments and we call them stage and testing . Somehow our testing environment was trying to perform a refresh session action by calling our stage environment. Have you every seen a similar issue? Can you give me a hint where should I look when debugging it? Here is a screen with error and our app config. Thanks!

Not available in the browser console

@User i made an event handler, but still not working

yeah, and that's necessary as well, but I think the

i18n.changeLanguage

(the function) is not getting called. so if you can get access to the

i18n

instance in the browser console (e.g., add

(window as any).i18n = i18n;

to

localization/index.ts

then you should be able to call the changelanguage in the browser.

you could also add logging into

translationFunc

(something like:

translationFunc: (key) => {console.log(key, i18n.t(key)); return i18n.t(key);},

and see what your translation function is returning.