Sentry's Flutter SDK 10.0: Streaming Traces and More Accurate Crash-Free Rates
Blog post from Sentry
Sentry’s Flutter SDK 10.0 introduces streaming traces as the default, sending completed spans in batches rather than waiting for an entire transaction to finish, while requiring developers to migrate custom instrumentation to span APIs or temporarily retain the previous transaction lifecycle. It improves Release Health accuracy by recording unhandled Flutter errors without classifying still-running sessions as crashed, and it creates a separately sampled app-start trace on Android and iOS with detailed startup timing measurements. The release removes separate enablement flags for logs and metrics, expands Dio failed-request capture to network failures without HTTP responses, and masks Flutter widgets marked as sensitive in Session Replay and screenshots. Version 10 requires newer Dart, Flutter, Android, iOS, and macOS versions, uses Swift Package Manager for Apple native SDK installation, removes profiling, changes some native crash and failed-request defaults, and directs users to the migration guide for upgrade-specific steps.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 5 | 1,841 | 506 | 164 | -62% |
| Observability | 1 | 1,359 | 336 | 123 | -50% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.