Vercel logs not showing enough information for next-auth issue?

[chelsea-tnc]

Google auth started failing in our production environment today (there haven't been changes shipped our codebase in about 4 days, no changes to our Vercel environment). A customer was using our platform fine earlier today, then we started seeing this auth issue.

When we try to login via Google auth, we see Vercel's "EDGE_FUNCTION_INVOCATION_FAILED" page. Vercel says to check the logs, so we do. But all we see in the Vercel function logs is the following:

/api/auth/callback/google
22:45:55:34
ID: gbhxp-xxxxxxxxxxxxx-xxxxxxxxxxxx
TypeError: Cannot read properties of undefined (reading 'name')
    at worker.js:40:2207
    at worker.js:40:3547
    at worker.js:40:3509
    at worker.js:40:5189
    at worker.js:40:4846
    at worker.js:40:3509
    at worker.js:40:5189
    at worker.js:40:4846
    at worker.js:40:3509
    at worker.js:40:5189

We obfcuscated the ID, though it's worth noting that it doesn't even match the UI's ID. However, it's the only error surfacing when we timed the issue exactly and the log repros consistently when we see the error in the UI.

We don't have a worker.js file anywhere in our codebase. Unsure how to proceed as we don't have an internal stack trace or more information from the logs. This issue only reproduces in production, not our staging or local dev environment, so breakpoints won't work with the code obfuscation in production (unless there is some way to remove that).

Has anyone seen this issue before (either with worker.js or with the Vercel log information being incomplete/inaccurate)?