nextjs deployment succeeded but landing page fails with Code: MIDDLEWARE_INVOCATION_FAILED

[chaotic-justice]

Description

middleware:

import { auth } from "@/auth"
import { routing } from "@/i18n/routing"
import { isAdmin } from "@/lib/utils"
import createIntlMiddleware from "next-intl/middleware"
import { NextRequest, NextResponse } from "next/server"

interface AppRouteHandlerFnContext {
  params?: Record<string, string | string[]>
}

const intlMiddleware = createIntlMiddleware({
  locales: routing.locales,
  defaultLocale: routing.defaultLocale,
  localePrefix: routing.localePrefix,
})

const homePages = ["/", "/signin"]
const authPages = ["/workers", "/images-uploader"]
const adminPages = ["/secret"]

const getPathnameRegex = (pages: string[]) => RegExp(`^(/(${routing.locales.join("|")}))?(${pages.flatMap((p) => (p === "/" ? ["", "/"] : p)).join("|")})/?$`, "i")

const homePathnameRegex = getPathnameRegex(homePages)
const authPathnameRegex = getPathnameRegex(authPages)
const adminPathnameRegex = getPathnameRegex(adminPages)

const authMiddleware = (request: NextRequest, ctx: AppRouteHandlerFnContext) => {
  return auth((req) => {
    const path = req.nextUrl.pathname
    const session = req.auth

    const isHomePage = homePathnameRegex.test(path)
    const isProtected = authPathnameRegex.test(path)
    const isAdminPage = adminPathnameRegex.test(path)

    if (session) {
      if (isHomePage) {
        return NextResponse.redirect(new URL("/workers", req.url))
      } else if (isAdminPage) {
        if (!isAdmin(session.user.email)) {
          console.log("not an admin", session.user.email)
          return NextResponse.redirect(new URL("/not-found", req.url))
        }
      }
    } else {
      if (isProtected || isAdminPage) {
        return NextResponse.redirect(new URL("/signin", req.url))
      }
    }

    return intlMiddleware(request)
  })(request, ctx)
}

export const middleware = (request: NextRequest, ctx: AppRouteHandlerFnContext): NextResponse => {
  if (request.nextUrl.pathname.startsWith("/auth")) {
    return NextResponse.next()
  }

  return authMiddleware(request, ctx) as NextResponse
}

export const config = {
  matcher: ["/((?!api|_next|_vercel|.*\\..*).*)"],
}

nextauth config:

import NextAuth, { DefaultSession } from "next-auth"
import Google from "next-auth/providers/google"

declare module "next-auth" {
  interface Session {
    user: {
      address?: string
      provider?: string
    } & DefaultSession["user"]
    error?: string
  }
}

export const { handlers, signIn, signOut, auth } = NextAuth({
  secret: process.env.AUTH_SECRET,
  callbacks: {
    // @ts-ignore
    async signIn({ user, account }) {
      //Allow OAuth without email verification
      if (account?.provider !== "credentials") return true
      // email verification logic here
      return true
    },
    // @ts-ignore
    async session({ token, session }) {
      if (token.userId && session.user) {
        session.user.id = token.userId as string
      }

      return session
    },
    async jwt({ token }: { token: any }) {
      return token
    },
  },
  providers: [
    Google({
      authorization: { params: { access_type: "offline", prompt: "consent" } },
    }),
  ],
})

error messages from logs

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

https://github.com/chaotic-justice/excel-stunning-pork

Reproduction description

Steps to reproduce:

1. Open reproduction
2. Click on …
3. See error: …

Expected behaviour

it works locally, deploys succesfully abut landing page will throw error

[github-actions]

Thank you for your report!

From the currently available context in this issue, it's unclear wether the erroneous behavior is caused by Next.js, next-intl or a 3rd party library that you're using. Please isolate the issue further to be sure that the issue is caused by next-intl. When in doubt, please search on the Next.js issue tracker or related resources of 3rd party libraries you might be using.

If you're able to isolate the issue to next-intl, please provide a minimal reproduction that ideally doesn't involve any 3rd party libraries or alternatively demonstrates that next-intl is causing the issue.

Thank you for your understanding!

[chaotic-justice]

cloned a repo off your app-router-with-next-auth example, deployed it, it works perfectly. i think this issue may be unrelated to next-intl. closign this