-
Notifications
You must be signed in to change notification settings - Fork 62
Description
Bug description
We're experiencing an issue where obfuscated stack traces in Flutter applications are not being deobfuscated in Datadog Error Tracking, despite successful symbol file uploads. This was working correctly before, but at some point, it stopped functioning.
Sample obfuscated stack trace:
*01 abs 00000074214516e3 virt 00000000009a26e3 kDartIsolateSnapshotInstructions+0x4fb763
Describe what you expected
Stack traces should be automatically deobfuscated and show readable Dart code locations (file names, line numbers, function names) instead of obfuscated memory addresses when all symbol upload requirements are met.
Steps to reproduce the issue
Environment Setup
Platform: Android
Flutter SDK: Using obfuscated builds with --obfuscate and --split-debug-info
Build Tool: Shorebird
Architecture: arm64, arm
Flutter Build Command
shorebird release android \ --artifact apk \ --flavor dev \ --target-platform android-arm,android-arm64 \ --build-number=1234567 \ --obfuscate \ --split-debug-info=build/app/outputs/symbols \ --release
Datadog Configuration
final configuration = DatadogConfiguration( clientToken: clientToken, env: 'dev', site: DatadogSite.us1, service: 'mobile.myapp', nativeCrashReportEnabled: true, flavor: 'dev', version: '2.1.0+1234567', firstPartyHosts: ['api.example.com', 'app.example.com'], loggingConfiguration: DatadogLoggingConfiguration(), );
Symbol Upload Results
Starting upload. Uploading Flutter Dart Symbol Files at location build/app/outputs/symbols version: 2.1.0+1234567 service: mobile.myapp flavor: dev ✅ Uploaded symbol 2 files in 22.914 seconds. Uploading Flutter Symbol File ./build/app/outputs/symbols/app.android-arm64.symbols Uploading Flutter Symbol File ./build/app/outputs/symbols/app.android-arm.symbols
Verification in RUM Debug Symbols Page
All matching criteria are satisfied:
Service: mobile.myapp ✅
Version: 2.1.0-1234567 (automatically converted from 2.1.0+1234567) ✅
Variant: dev ✅
Architecture: Both arm and arm64 present ✅
Type: Flutter ✅
Upload Time: Recent (within processing window) ✅
Result
Despite all requirements being met, stack traces remain obfuscated and are not deobfuscated.
Questions:
Has this issue been reported before? Are there similar cases where all symbol upload requirements are met but deobfuscation still fails?
What are the recommended troubleshooting steps? Is there a systematic approach to resolve this type of issue when all matching criteria appear to be satisfied?
Additional context
This issue started occurring recently - deobfuscation was working correctly before
All matching criteria appear to be satisfied according to the documentation
We've tested with fresh deployments and new versions, but the issue persists
Both arm and arm64 symbol files are being uploaded successfully
We've waited well beyond the documented 5-minute processing window
Command
None