Closed Pratham271 closed 4 months ago
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
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 (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.
The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
Depending on the reason the issue was closed, you can do the following:
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.
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:
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
We look into every Next.js issue and constantly monitor open issues for new comments.
However, sometimes we might miss one or two 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.
Link to the code that reproduces this issue
not public
To Reproduce
NA
Current vs. Expected behavior
current Getting the error
Expected When the user logs in he/she should be redirected to chat page
Provide environment information
Which area(s) are affected? (Select all that apply)
Runtime
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed)
Additional context
TypeError: Invalid URL string. at (src/middleware.ts:14:21) at (node_modules/next-auth/next/middleware.js:72:0) at (node_modules/next-auth/next/middleware.js:54:0) at (node_modules/next-auth/next/middleware.js:68:0) at (node_modules/next/dist/esm/server/web/adapter.js:158:0)
[GET] [middleware: "src/middleware"] /chat reason=EDGE_FUNCTION_INVOCATION_FAILED, status=500, user_error=true
these are the errors I am getting in the logs middleware.ts file
NEXT_PUBLIC_BASE_URL=https://enigma-chatpdf.vercel.app