-
Notifications
You must be signed in to change notification settings - Fork 26.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Boundaries is not catching error from Server side component #63451
Comments
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 (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.
What should I do?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. My repository is private and cannot make it publicIn 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:
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 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. Useful Resources |
Link to the code that reproduces this issue
For data security we cant give any code base link. Please reproduce by following below steps
To Reproduce
Step To Reproduce this Issue
1- Create error.tsx file in app folder to catch error of entire application
2- If error is coming for client side component it is working fine
3 - Create custom hook (to handle API call in our application) in components folder outside app folder , because app folder contains only routes components
4 - If error is coming from server side components , it is not catching by error.tsx file
Current vs. Expected behavior
Current Behaviour of Error Boundary
Expected Behavior of Error Boundary:
-like components should catch server errors without needing to be implemented as Route Segment error.tsx files.
Provide environment information
Operating System: Platform: windows version: windows 11 Binaries : Node: v20.11.0 Yarn: 1.22.19 Relevant Package: next: 14.1.0 react: ^18 react-dom: ^18 typescript: ^5
Which area(s) are affected? (Select all that apply)
App Router
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local)
Additional context
No response
The text was updated successfully, but these errors were encountered: