K
Kinde2mo ago
母雞王

Is the Expo SDK buggy with Expo Go?

After the first authentication flow, callbacks stop working. I was told by the Kinde AI that "This is a known issue with the Expo SDK when using Expo Go. The callbacks stop working after the first authentication flow because of how Expo Go handles deep links and app state restoration"
10 Replies
Roshan
Roshan2mo ago
Hi there, Thanks for reaching out. Please check the following. What platform are you using? (iOS or Android) Could you confirm that you are using the latest version of the SDK? Could you please try clearing the cache and check again? Could you ensure that your configuration is correct? After checking these things, if you are still having an issue, could you share your current implementation and configuration? If you want to keep the above details private, you can create a ticket.
母雞王
母雞王OP2mo ago
Android "expo": "^53.0.17", "@kinde/expo": "^0.5.0", tried clearing the cache but it remains it's just like the docs: <KindeAuthProvider //For testing callbacks={ { onSuccess: async (user, state, context) => { console.log("User authenticated:", user); }, onError: async(error, state, context) => { console.error("Authentication error:", error); }, onEvent: async (event, state, context) => { console.log("Authentication event:", event); } } } config={{ domain: process.env.EXPO_PUBLIC_KINDE_ISSUER_URL, clientId: process.env.EXPO_PUBLIC_KINDE_CLIENT_ID, }} > (provider in the root _layout) const kinde = useKindeAuth(); const handleSignIn = async () => { console.log("Sign in pressed"); const token = await kinde.login(); console.log("After login, token:", token); if (token) { console.log("User signed in:", token); } }; that's the sign in. it stays in the stack screen header
Roshan
Roshan2mo ago
Hi there, Thanks for providing the details. Did you check your configuration in the Kinde dashboard? Additionally, could you please check the .env file and attempt to log it?
母雞王
母雞王OP2mo ago
this is my kinde setup for the app in the kinde dashboard the .env is being recognized fine, i am able to log in and logout as many times as i want, but the callbacks are not being executed, nor anything i write after const token = await kinde.login() in the handlesignin function. Gemini told me it was because of faulty promise handling (because of deep linking related issues, and kinde ai told me the issues were because of expo go)
No description
Roshan
Roshan2mo ago
Hi there, Thanks for providing the details again. I will reach out to our engineering team on your query and will get back to you. Hi there, Our engineering team has tried to replicate your issue with the exact same config and code, but it works fine on our end. Could you try to build from scratch again?
母雞王
母雞王OP2mo ago
check it out. made it from a brand new expo project. these are the logs: i pressed login and logged in. then pressed login again and logged in again. (but only 1 log).
母雞王
母雞王OP2mo ago
and not from a callback i used expo go in this example btw i also tried the original project with a development build and it also didnt work
Roshan
Roshan2mo ago
Hi there, I've attached screenshots of what we've tried to replicate your issue.
No description
No description
No description
No description
No description
母雞王
母雞王OP2mo ago
why is the callback url api_? could you send me your code please? interesting... alert worked for me why do console.logs not work in the callbacks then?
Roshan
Roshan2mo ago
I am not sure about that, but as far as the alert works, I think the issue is not related to the SDK. :)

Did you find this page helpful?