The In App vs NextAuth problem
If you open the app link from a mobile app (like discord/telegram) and it opens in the in-app browser instead of the default browser, the Sign up will fail.
Does anyone recommend any way to deal with this?
I'm not sure if NextAuth has an option to allow built-in browsers, but I couldn't find anything.
My other idea was to prompt the user to open the default browser instead, but this sucks
Does anyone recommend any way to deal with this?
I'm not sure if NextAuth has an option to allow built-in browsers, but I couldn't find anything.
My other idea was to prompt the user to open the default browser instead, but this sucks
Solution
Thanks for the answer.
I'm not exactly sure if the built-in browser was the problem, it was more of a guess.
My friend and coworker @BigLung fixed it with the help of this post https://github.com/nextauthjs/next-auth/issues/519#issuecomment-1326847336
I'm not exactly sure if the built-in browser was the problem, it was more of a guess.
My friend and coworker @BigLung fixed it with the help of this post https://github.com/nextauthjs/next-auth/issues/519#issuecomment-1326847336
GitHub
Describe the bug In your next-auth-example, default login screen (http://localhost:3000/api/auth/signin) I added TWITTER_ID and TWITTER_SECRET and DATABASE_URL to .env.local added all these callbac...
Similar Threads
Was this page helpful?
