[Bug] 全屏错误提示 “Something went wrong!”

[Hwwwww-dev]

当出现某些报错的时候，会全屏出现报错。
应该加强异常的捕获，使用通知的形式提示错误，而非全屏错误影响体验。

Something went wrong!
Failed to fetch
Try again

[github-actions]

Thank you for reporting this issue.

Analysis:

Based on the screenshot and error message ("Something went wrong!" + "Failed to fetch"), this fullscreen error is triggered by Next.js's global-error.tsx component, which is the fallback error boundary for the entire application.

Root Cause:

The project has a hierarchical error handling structure:

1. src/app/global-error.tsx (lines 9-60) - The fullscreen error boundary you're seeing. This catches errors at the root layout level and displays a fullscreen error page because it must replace the entire HTML/body when the root layout fails.

2. src/components/error-boundary.tsx (lines 23-52) - A more graceful component-level error boundary that displays errors inline within a Card component.

3. Toast notifications - Already implemented via sonner (src/components/ui/sonner.tsx) and used in many components (e.g., src/app/[locale]/dashboard/_components/statistics/wrapper.tsx uses toast.error() for fetch failures).

The "Failed to fetch" error suggests a network request failed (e.g., API call, fetch to backend). When this error propagates up and isn't caught by a component-level error boundary, it reaches the global error boundary and triggers the fullscreen view.

Current Error Handling:

• Many components already use toast notifications for errors (verified in 44+ files)
• Component-level ErrorBoundary and ListErrorBoundary exist for inline error display
• However, some uncaught fetch errors can still bubble up to the global level

To help diagnose this specific scenario:

• What page/action triggered this error?
• Can you reproduce it consistently? If so, what are the steps?
• Is this happening with a specific API call or component?
• Are there any browser console errors that provide more context?

This information will help identify which specific component or data fetch needs additional error boundary coverage or needs to handle errors gracefully with toast notifications instead of throwing.

---

Automated response from Claude AI

[ding113]

后续会优化报错体验。