This page describes the Flutter SDK support scope and current limits so you can determine whether your project meets the requirements before integration.
Support scope
Packages and capabilities
Dart class names begin with Datadog*, and the site enum is FlashcatSite. Use the default .cn site for customer-facing production environments; configure the full customEndpoint for on-premises deployments. The DatadogSdk, DatadogConfiguration, DatadogRumConfiguration, DatadogNavigationObserver, and other classes in the documentation examples are the actual exported class names.
Supported automatic collection
Current limits
Symbolication compatibility
Flutter crash stacks can contain both Dart frames and native (iOS / Android) frames. To resolve stack frames back to source locations, you need to upload the corresponding symbol files:
Dart stacks cannot be symbolicated on iOS yet. The symbol file Flutter produces for Apple targets is a Mach-O, and the platform currently parses only the ELF format used on Android, so an iOS .symbols upload is rejected. iOS native crashes are unaffected — upload dSYMs to symbolicate them.If you ship both iOS and Android, you can still enable --obfuscate: Android Dart stacks resolve normally while iOS Dart stacks stay obfuscated. If readable iOS stacks matter more, leave --obfuscate off for that platform’s build.
Symbol files are uploaded through the FlashCat CLI. Symbols are matched to crash events by the build’s build ID, so you need to upload a fresh set of symbol files after every code change.
