[Megaissue] Mobile error tracking #38845
Description
Features
High priority
- Filtering by release
- "Unhandled" should be more than a boolean (move to an enum)
- Mobile versions last longer so it's important to bump the priority of the "releases" concept e.g. resolve an issue up to this release
Medium priority
- Client side suppression rules will not worked the same because the "type" will be minified
- Do we need more configuration for exception autocapture
- Mobile supports sources (filenames), packages (com.posthog.error_tracking) and modules (e.g. 3rd party package)
- Device type and OS version matter more on mobile. We should define a list of properties to breakdown by on each platform
- Multithreading needs to be considered because we might need context from other threads
- Knowing how early into a session an exception happens is an important signal
- Breadcrumbs become more important to help people debug because the individual stack traces might be less useful (e.g. if the stack trace is an OS system)
Sequencing
Straightforward
React Native (JS only layer) Error tracking/Mobile team
- Inject chunk ids to JS files - Hugues
- Upload command in the CLI - Olly
- Bundler plugin to do the above at the right moments - Manoel
- Build an Expo plugin to simplify all of the above configuration - Manoel
Flutter (1 week)
- New raw frame type in cymbal (no need for line context)
- SDK exception manual capture
- SDK exception auto capture
Android (1 month)
- New raw frame type in cymbal (no need for line context)
- SDK manual
- SDK autocapture (hard crashes)
- Hook into build system with CLI
- Add symbolification with Proguard / Gradle (~2-3 weeks)
React Native plugin <-- Manoel
- React Native plugin for native exceptions (only for Android)
More complicated
Swift <-- Ioannis
TBD