symbolication-setup
Skill116 starsChanged 11 months agoMITView on GitHub
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crash-instrumentationSkill
- instrumentation-planningSkill
- interaction-latencySkill
- navigation-latencySkill
- network-tracingSkill
- session-replaySkill
- user-journey-trackingSkill
The file
Files
Symbolication Setup
Make crash stack traces readable instead of memory addresses or minified code.
Why It Matters
Without symbolication:
0x104a3b2c8 <redacted> + 123With symbolication:
PaymentViewController.processPayment() line 47Unsymbolicated crashes are useless for debugging.
Platform Setup
iOS (dSYMs)
Xcode Build Phase Script:
# Add to Build Phases → New Run Script Phase
if [ "${CONFIGURATION}" = "Release" ]; then
# Sentry
sentry-cli upload-dif --include-sources "${DWARF_DSYM_FOLDER_PATH}"
# Or Crashlytics
"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" \
-gsp "${PROJECT_DIR}/GoogleService-Info.plist" \
-p ios "${DWARF_DSYM_FOLDER_PATH}"
fiFind missing dSYMs:
# Recent archives
find ~/Library/Developer/Xcode/Archives -name "*.dSYM" -mtime -7
# Verify UUID matches
dwarfdump --uuid MyApp.app.dSYMAndroid (ProGuard/R8)
build.gradle.kts:
android {
buildTypes {
release {
isMinifyEnabled = true
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro"
)
}
}
}
// Sentry auto-upload
sentry {
autoUploadProguardMapping.set(true)
uploadNativeSymbols.set(true)
}
// Or manual upload in CI
// sentry-cli upload-proguard --android-manifest app/build/.../AndroidManifest.xml mapping.txtKeep rules for crash reporting:
# proguard-rules.pro
-keepattributes SourceFile,LineNumberTable
-renamesourcefileattribute SourceFile
# Keep Sentry classes
-keep class io.sentry.** { *; }React Native (Source Maps)
Expo (app.json):
{
"expo": {
"plugins": [
["@sentry/react-native/expo", {
"organization": "your-org",
"project": "your-project"
}]
],
"hooks": {
"postPublish": [{
"file": "sentry-expo/upload-sourcemaps"
}]
}
}
}Bare React Native (CI):
# After build
sentry-cli releases files $VERSION upload-sourcemaps \
--dist $BUILD_NUMBER \
./build/sourcemapsHermes bytecode:
# Hermes requires source maps - verify with:
sentry-cli sourcemaps explain <event-id>Verification Checklist
- Release builds upload symbols automatically
- CI pipeline includes symbol upload step
- Test crash shows readable stack trace
- Source maps include original source (not just line numbers)
- Build numbers match between app and uploaded symbols
Common Issues
| Symptom | Cause | Fix |
<redacted> in stack | Missing dSYM | Upload dSYM for that build |
| Line numbers wrong | Source map mismatch | Verify release/dist strings match |
| Only framework symbols | App dSYM missing | Check archive includes app dSYM |
<unknown> in RN | Hermes without source maps | Configure Hermes source map generation |
Vendor Commands
| Vendor | Verify Upload |
| Sentry | sentry-cli debug-files check <UUID> |
| Crashlytics | Firebase Console → Crashlytics → Missing dSYMs |
| Bugsnag | bugsnag-cli upload with --dry-run |
| Datadog | Dashboard → Error Tracking → Symbol Files |
| bitdrift | Dashboard or CLI for dSYM, Gradle plugin for ProGuard |
| New Relic | iOS dSYM via build script or newrelic-cli; Android ProGuard auto-uploaded by NR Gradle plugin |
Related Skills
- See
skills/crash-instrumentationfor breadcrumb strategies and crash context - Symbolication is Tier 1 in
skills/instrumentation-planning
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

