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
2 Replies
The best way. I can think is to have a growing list of those in-app browsers to detect and add an interrupt screen with directions on how to open the link.
Definitely not ideal, but my expectation (and quick research) would be that it's an app setting to offer and use such a browser. So I think the apps would then have to provide a way for you to bypass it.
Getting NextAuth to work with the in-app browsers might be a better road to travel. I haven't used it but I'd be curious why it doesn't work that way and if other auth services do. Either approach seems like something that'd be helpful to have NextAuth handle itself.
(This did finally urge me to go disable those in-app browsers for gmail and discord, ty!)
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
GitHub
Keep getting redirected with error: OAuthAccountNotLinked · Issue #...
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...