fix:[next-international] Locale not found in headers or cookies, returning "notFound()"

[ivan-kadyka]

First of all, @QuiiBz, thank you for your great library!

Problem:
executing server function 'getCurrentLocale' can cause error: '[next-international] Locale not found in headers or cookies, returning "notFound()"'

Description:
When users authenticate via OAuth (Google provider), the callback redirect from Google's servers to our application doesn't include the locale cookie due to the sameSite: 'strict' setting. This results in getCurrentLocale() returning undefined during the authentication callback.

OAuth redirects:

1. 'your-website.com'
2. 'oauth-website.com '
3. 'your-website.com'

My use case:
Google OAuth with 'next-auth' library and 'events' configuration

  export const authOptions: AuthOptions = {
  adapter: PrismaAdapter(prisma),
  providers: [
    Google({
      clientId: env.GOOGLE_CLIENT_ID,
      clientSecret: env.GOOGLE_CLIENT_SECRET
    })],
  events: {
    async signIn({ user }) {
       
    const locale = await getCurrentLocale()
    // locale is undefined
    // '[next-international] Locale not found in headers or cookies, returning "notFound()"' 
    // google auth url:  https://accounts.google.com/o/oauth2/v2/auth/oauthchooseaccount

    // sending analytics how locale information is used
     
    }}
    ...
  }

Solution:
Storing information about the user's selected locale is not strictly secure. Change the locale cookie setting to use the browser default (sameSite: 'lax').

[vercel]

@ivan-kadyka is attempting to deploy a commit to the Tom Labs Team on Vercel.

A member of the Team first needs to authorize it.

[dnil-hcom]

This is also an issue with link scanners that are built into outlook, teams etc.