PostHog / PostHog/posthog-flutter
Capture errors from background isolates
Open
Nobody has claimed this yet.
enhancement
feature/error-tracking
- Dominant language
- Dart
- Stars
- 97
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Extracted from PostHog/posthog#43012.
Problem
The error listener attaches only to the isolate that runs install() (the main one), so uncaught errors in user-spawned background isolates aren't captured. The config docstring also overclaims coverage of "any isolates spawned."
Scope
- Capture uncaught errors from background isolates.
- Fix the docstring to match actual behavior in the same change.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating install(), the error listener, and the configuration docstring in the Flutter SDK. Trace how user-spawned background isolates are created and how uncaught errors are forwarded, then add or update coverage for those errors and verify that the docstring accurately describes the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100