skills.rest
Turgunoff
TurgunoffCOMMUNITY
Explore all skills by this author →
GitHub

source-command-symbolize

Decodes obfuscated Dart crash stack traces using Flutter symbol files.

Updated May 11, 2026
Search Tags:#debugging#stack trace#flutter#dart#crashlytics#symbolize#crash decoding
One-click install
npx skills add https://github.com/Turgunoff/mebellar_app --skill source-command-symbolize-turgunoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-symbolize
Source: https://github.com/Turgunoff/mebellar_app/tree/main/.agents/skills/source-command-symbolize
Command: npx skills add https://github.com/Turgunoff/mebellar_app --skill source-command-symbolize-turgunoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Crashlytics crash reports for Flutter release builds contain obfuscated stack traces with no readable file paths or line numbers, making production bugs nearly impossible to locate without the matching debug symbols. ## Core Features & Use Cases - Stack Trace Decoding: Runs flutter symbolize against the correct build/symbols/ file to convert obfuscated frames into real file paths and line numbers. - Architecture Detection: Infers the target ABI (arm64, arm, x64, iOS) from the trace and falls back to alternate symbol files if the first attempt fails. - Bug Localization: Highlights the first non-Flutter-framework frame, which is almost always the actual crash location. - Use Case: A Crashlytics alert shows an obfuscated crash from the latest Play Console release; paste the trace and get back the exact Dart file and line responsible. ## Quick Start Paste the obfuscated Crashlytics stack trace and ask to symbolize it using the release symbols in build/symbols/.

Frequently Asked Questions about source-command-symbolize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decode an obfuscated Flutter crash stack trace?▼

Write the obfuscated trace to a file and run flutter symbolize with the -i flag pointing to that file and -d pointing to the matching symbol file in build/symbols/. The output shows real Dart file paths and line numbers for each frame.

How to symbolize a Crashlytics crash for a Flutter Android release?▼

Detect the ABI from the trace, defaulting to arm64, then run flutter symbolize against app.android-arm64.symbols. If decoding fails, retry with the arm or x64 symbol files until the frames resolve.

Why does flutter symbolize fail with missing build/symbols directory?▼

Symbol files are generated per release build and only decode crashes from that exact app-release.aab version. Without the matching symbols, no decode is possible, so keep a copy of build/symbols/ for every release uploaded to Play Console.

Which frame in a decoded Flutter stack trace shows the actual bug?▼

The first non-Flutter-framework frame is almost always the actual bug location. Framework frames describe internal engine or widget machinery, while your app's own code frame points to the source of the crash.

Can I symbolize iOS Flutter crashes with the same symbol files?▼

No, iOS builds produce a separate app.ios.symbols file. Use that file with flutter symbolize when the crash originates from an iOS release rather than an Android ABI-specific symbol file.

Related Skills

Explore More Software Engineering Skills→
CANTAGESTUDIOCANTAGESTUDIO
3

flutter-obfuscate-docs

Obfuscate Flutter builds and generate symbol files for crash deobfuscation.

Community
Advanced
float-ritual-stackfloat-ritual-stack

rule-audit

Scan .claude/rules for backtick-wrapped paths and line references against the codebase.

Official
Advanced
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

crash-analytics

Analyze crash reports and rank stability issues by release impact.

Community
Advanced
PostHogPostHog
713

diagnosing-stacktrace-symbolication

Diagnose PostHog Error Tracking stack-trace symbolication failures across JavaScript, React Native, Android, and iOS builds.

Official
Advanced