github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-10 21:03:06 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #7391] [Maintenance] Add scoped ErrorBoundaries to isolate feature-level crashes #10009

New Issue
Open
opened 2026-04-10 20:20:47 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-10 20:20:47 -05:00
Owner
Copy Link

Originally created by @MatissJanis on GitHub (Apr 5, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7391

Summary

When a component throws a rendering error, the entire app crashes to the "Fatal Error" screen. This happens because we only have two top-level ErrorBoundary wrappers (in App.tsx) and one feature-scoped boundary (in GetCardData.tsx for report charts).

Adding scoped ErrorBoundary components around major features would contain failures to the affected area instead of taking down the whole app.

Problem

A single rendering error in any feature — budget, accounts, transactions, reports, schedules, rules — crashes the entire application. Users lose all context and must restart.

This is a recurring pattern. Across open and closed issues, there are 70+ reports of fatal crashes caused by component-level errors that could have been contained:

Currently open:

  • #7273 — Fatal Error after reports .json file import
  • #7285 — Fatal Error viewing ledgers with recurring transactions ending in the past
  • #7098 — Custom Report bars crash
  • #7108 — Calendar widget crashes on mobile
  • #6073 — Hide reconciled transactions crashes app
  • #7358 — Dollar sign in Schedule Name crashes app
  • #6317 — Backslash in rule notes causes crash
  • #5351 — API Unhandled Rejection

Recurring crash patterns from closed issues:

The fix for #4703 (adding an ErrorBoundary around modals) shows this approach works. We should apply it systematically.

Proposed approach

Wrap major feature areas with ErrorBoundary from react-error-boundary (already a dependency at v6.0.3). Each boundary should:

  1. Catch and contain the error to that feature area
  2. Show a contextual fallback (e.g., "This report couldn't be loaded" instead of a full-app fatal screen)
  3. Offer a retry via resetErrorBoundary where it makes sense

Suggested areas to add boundaries

Area Entry point(s) Related crashes
Budget table BudgetTable / BudgetPageHeader #5969, #6073
Account ledger Account component #7285, #3263, #595
Transaction list TransactionList #5304, #1021
Reports (individual) Each report view #7273, #7098, #5814, #5764, #6221
Schedules Schedules page #7358, #3989, #3954
Rules Rules page #6317, #6885, #4013, #2180
Sidebar Sidebar component #5467
Dashboard widgets Individual widget cards #7108, #6313
Individual modals Each modal content (container boundary exists) #4703 pattern

Implementation notes

  • react-error-boundary v6 is already a dependency — no new packages needed
  • FatalError.tsx has good patterns for error display that can be adapted
  • A shared FeatureErrorFallback component could keep UX consistent across boundaries
  • Each boundary can use onError to log to the existing notification system

This is a good first contribution

Each boundary is a small, self-contained change — pick one area from the table above. The pattern is straightforward:

import { ErrorBoundary } from 'react-error-boundary';

<ErrorBoundary FallbackComponent={FeatureErrorFallback}>
  <YourFeatureComponent />
</ErrorBoundary>
Originally created by @MatissJanis on GitHub (Apr 5, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7391 ## Summary When a component throws a rendering error, the entire app crashes to the "Fatal Error" screen. This happens because we only have two top-level `ErrorBoundary` wrappers (in `App.tsx`) and one feature-scoped boundary (in `GetCardData.tsx` for report charts). Adding scoped `ErrorBoundary` components around major features would contain failures to the affected area instead of taking down the whole app. ## Problem A single rendering error in any feature — budget, accounts, transactions, reports, schedules, rules — crashes the entire application. Users lose all context and must restart. This is a recurring pattern. Across open and closed issues, there are **70+ reports** of fatal crashes caused by component-level errors that could have been contained: **Currently open:** - #7273 — Fatal Error after reports .json file import - #7285 — Fatal Error viewing ledgers with recurring transactions ending in the past - #7098 — Custom Report bars crash - #7108 — Calendar widget crashes on mobile - #6073 — Hide reconciled transactions crashes app - #7358 — Dollar sign in Schedule Name crashes app - #6317 — Backslash in rule notes causes crash - #5351 — API Unhandled Rejection **Recurring crash patterns from closed issues:** - **Filter condition changes** (is ↔ one-of switching) — #6446, #6479, #6325, #6452, #6590, #5476, #5347 - **Reports/charts rendering** — #6221, #5814, #5729, #5764, #6406, #1792, #4307 - **Rules and schedules** — #6885, #6422, #6160, #5258, #4013, #3989, #3954, #2180 - **Date field handling** — #5304, #5094, #5969 - **Mobile/browser-specific** — #6650, #6467, #5692, #4204, #3263 - **Modals** — #4703 (fixed by adding an ErrorBoundary — proving the pattern works) The fix for #4703 (adding an ErrorBoundary around modals) shows this approach works. We should apply it systematically. ## Proposed approach Wrap major feature areas with `ErrorBoundary` from `react-error-boundary` (already a dependency at v6.0.3). Each boundary should: 1. **Catch and contain** the error to that feature area 2. **Show a contextual fallback** (e.g., "This report couldn't be loaded" instead of a full-app fatal screen) 3. **Offer a retry** via `resetErrorBoundary` where it makes sense ### Suggested areas to add boundaries | Area | Entry point(s) | Related crashes | |------|----------------|-----------------| | Budget table | `BudgetTable` / `BudgetPageHeader` | #5969, #6073 | | Account ledger | `Account` component | #7285, #3263, #595 | | Transaction list | `TransactionList` | #5304, #1021 | | Reports (individual) | Each report view | #7273, #7098, #5814, #5764, #6221 | | Schedules | `Schedules` page | #7358, #3989, #3954 | | Rules | `Rules` page | #6317, #6885, #4013, #2180 | | Sidebar | `Sidebar` component | #5467 | | Dashboard widgets | Individual widget cards | #7108, #6313 | | Individual modals | Each modal content (container boundary exists) | #4703 pattern | ### Implementation notes - `react-error-boundary` v6 is already a dependency — no new packages needed - `FatalError.tsx` has good patterns for error display that can be adapted - A shared `FeatureErrorFallback` component could keep UX consistent across boundaries - Each boundary can use `onError` to log to the existing notification system ## This is a good first contribution Each boundary is a small, self-contained change — pick one area from the table above. The pattern is straightforward: ```tsx import { ErrorBoundary } from 'react-error-boundary'; <ErrorBoundary FallbackComponent={FeatureErrorFallback}> <YourFeatureComponent /> </ErrorBoundary> ```
GiteaMirror added the tech debtgood first issuemaintenancehelp wanted labels 2026-04-10 20:20:48 -05:00
GiteaMirror commented 2026-04-10 20:20:49 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 5, 2026):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don't forget to upvote the top comment with 👍!

<!-- gh-comment-id:4189503724 --> @github-actions[bot] commented on GitHub (Apr 5, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don't forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label good first issue help wanted maintenance tech debt
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#10009
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?