TypeError ("response" must be instance of Response), SvelteKit, Provider: Google

[notarib-catcher]

Environment

System:

• OS: Windows 10 10.0.22621
• CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
• Memory: 4.44 GB / 15.35 GB Binaries:
• Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
• Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
• npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
• pnpm: 7.17.1 - C:\Program Files\nodejs\pnpm.CMD Browsers:
• Edge: Chromium (118.0.2088.61)
• Internet Explorer: 11.0.22621.1

Reproduction URL

https://falak.mitblrfest.in

Describe the issue

I am hosting my sveltekit site on Vercel's Hobby plan, we're using authjs for sveltekit with google as the provider to authenticate users. The version of Authjs I'm using in live is @auth/sveltekit 0.3.10, the error is occuring even when I update to 0.3.11 (latest) The error seems to be a TypeError that occurs when attempting to login. So far, I have only attempted this with the google auth provider.

To be completely honest, I am at a loss for why this error is occuring.

• The error only occurs on live production and not on dev deployments - Login works fine on dev
• I am unable to reproduce it on the local dev server (vite dev)
• The error came up without intervention: We made a new deployment with CSS and some text changes that triggered it
• The error seems to have come up after the vercel incident last night (Degraded performance: Assigning domains) however, this may also be coincidence.

How to reproduce

Since this error is rather specific to my deployment, I cannot provide a proper steps-to-reproduce, however here is the error log from vercel's runtime logs

[POST] /auth/signin/google

[auth][cause]: TypeError: "response" must be an instance of Response
    at Module.processDiscoveryResponse (file:///var/task/node_modules/oauth4webapi/build/index.js:212:15)
    at getAuthorizationUrl (file:///var/task/node_modules/@auth/core/lib/oauth/authorization-url.js:19:28)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Module.signin (file:///var/task/node_modules/@auth/core/lib/routes/signin.js:15:20)
    at async AuthInternal (file:///var/task/node_modules/@auth/core/lib/index.js:112:36)
    at async Auth (file:///var/task/node_modules/@auth/core/index.js:100:30)
    at async respond (file:///var/task/.svelte-kit/output/server/index.js:2523:22)
    at async Server.default (file:///var/task/.svelte-kit/vercel-tmp/index.js:47:3)
    at async Server.<anonymous> (/var/task/___vc/__launcher/__launcher.js:14:11367)

[auth][details]: {
  "provider": "google"
}

[auth][error][SignInError]: Read more at https://errors.authjs.dev#signinerror

This is a novel error in prod, I hope you'll excuse me for providing less-than-adequate explanations, but I am in a relative hurry to get this fixed 😅

Expected behavior

The user should be logged in with google

[github-actions[bot]]

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository. Example: (NextAuth.js example repository).

The bug template that you filled out has a section called "Reproduction URL", which is where you should provide the link to the reproduction.

• If you did not provide a link or the link you provided is not valid, we will close the issue.
• If you provide a link to a private repository, we will close the issue.
• If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

• If you did not provide a link, please open a new issue with a link to a reproduction.
• If you provided a link to a private repository, please open a new issue with a link to a public repository.
• If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

• Remove any code that is not related to the issue. (pages, API Routes, components, etc.)
• Remove any dependencies that are not related to the issue.
• Remove any third-party service that would require us to sign up for an account to reproduce the issue.
• Remove any environment variables that are not related to the issue.
• Remove private packages that we do not have access to.
• If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every issue and monitor open issues for new comments.

However, sometimes we might miss a few due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to create a Minimal, Complete, and Verifiable example
• Bug report: Framework
• Bug report: Provider
• Bug report: Adapter