Crashlytics Gradle 플러그인은 코드 난독화 시점을 자동으로 감지할 수 있습니다. 빌드 시 매핑 파일이 생성되면 플러그인이 해당 파일을 업로드하며, Crashlytics 서버는 이 파일을 사용하여 앱의 스택 트레이스를 사람이 읽을 수 있는 가독화된 코드로 렌더링합니다.
R8, ProGuard, DexGuard 사용 시 필요한 구성
Crashlytics는 ProGuard와 호환되는 모든 매핑 파일을 가독화할 수 있으며 ProGuard, R8, DexGuard를 사용해 추가로 테스트되었습니다.
앱이 Android Gradle 4.2.0 이상과 함께 난독화 기능이 사용 설정된 상태에서 R8를 사용하는 경우 Crashlytics가 읽을 수 있는 비정상 종료 보고서를 생성합니다. Crashlytics에서 최근에 Kotlin과 R8을 둘 다 사용하는 앱에 대한 지원이 개선되었으나, 이로 인해 예상치 못한 라벨 지정 문제가 발생할 수 있습니다.
앱이 ProGuard 구성 파일을 사용하는 경우 Crashlytics에서 읽을 수 있는 비정상 종료 보고서를 생성하는 데 필요한 정보를 보존해야 합니다. ProGuard 또는 DexGuard 구성 파일에 다음 줄을 추가하면 됩니다.
-keepattributesSourceFile,LineNumberTable# Keep file names and line numbers.-keeppublicclass*extendsjava.lang.Exception# Optional: Keep custom exceptions.
Crashlytics Gradle 플러그인이 난독화를 사용하는 변형의 매핑 파일을 업로드하지 않도록 하려면 모듈(앱 수준) Gradle 파일(일반적으로 <project>/<app-module>/build.gradle.kts 또는 <project>/<app-module>/build.gradle)에서 firebaseCrashlytics.mappingFileUploadEnabled Gradle 확장 속성을 false로 설정하세요. 이렇게 하면 난독화된 빌드의 빌드 시간을 단축할 수 있지만 생성된 스택 트레이스는 Firebase Console의 Crashlytics 페이지에 난독화되어 표시됩니다.
Kotlin
importcom.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension// ...android{// To enable Crashlytics mapping file upload for specific build types:buildTypes{getByName("debug"){minifyEnabled=trueconfigure<CrashlyticsExtension>{mappingFileUploadEnabled=false}}}...// To enable Crashlytics mapping file upload for specific product flavors:flavorDimensions+="environment"productFlavors{create("staging"){dimension="environment"...configure<CrashlyticsExtension>{mappingFileUploadEnabled=false}}create("prod"){dimension="environment"...configure<CrashlyticsExtension>{mappingFileUploadEnabled=true}}}}
Groovy
android{// To enable Crashlytics mapping file upload for specific build types:buildTypes{debug{minifyEnabledtruefirebaseCrashlytics{mappingFileUploadEnabledfalse}}}...// To enable Crashlytics mapping file upload for specific product flavors:flavorDimensions"environment"productFlavors{staging{dimension"environment"...firebaseCrashlytics{mappingFileUploadEnabledfalse}}prod{dimension"environment"...firebaseCrashlytics{mappingFileUploadEnabledtrue}}}}
[null,null,["최종 업데이트: 2025-08-29(UTC)"],[],[],null,["\u003cbr /\u003e\n\niOS+ Android Flutter Unity \n\n\u003cbr /\u003e\n\nBy default, Firebase Crashlytics automatically processes your debug symbol\n(dSYM) files to give you deobfuscated and human-readable crash reports. You\nusually configure this behavior during the initial setup of Crashlytics in\nyour app, specifically by\n[adding a run script](/docs/crashlytics/get-started?platform=ios#set-up-dsym-uploading)\nthat automatically uploads dSYM files during your app's build phase.\n\nUnfortunately, there are a few cases that could cause your automatic dSYM files\nupload to fail. This guide provides some ways to troubleshoot when\nCrashlytics can't locate your app's dSYM files.\n\nMake sure Xcode can automatically process dSYMs and upload the files\n\nWhen setting up Crashlytics in your app, you\n[configured a run script](/docs/crashlytics/get-started?platform=ios#set-up-dsym-uploading)\nto automatically process dSYMs and upload the files.\n\nMake sure that your configuration for the Crashlytics run script is\nup-to-date with the new requirements which started with Xcode 15. If your\nconfiguration isn't up-to-date, you might be getting the following error: \n\n`error: Info.plist Error Unable to process Info.plist at path ...`.\n\nSpecifically, Xcode 15 and later requires that you provide a more complete set\nof file locations. For your Crashlytics run script\n(`firebase-ios-sdk/Crashlytics/run`), make sure that you have the following\nsetup:\n\n1. Click the **Build Phases** tab, and then expand the *Run Script* section.\n\n2. In the *Input Files* section, make sure you have the paths for the locations\n of the following files:\n\n ```\n ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}\n ``` \n\n ```\n ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${PRODUCT_NAME}\n ``` \n\n ```\n ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Info.plist\n ``` \n\n ```\n $(TARGET_BUILD_DIR)/$(UNLOCALIZED_RESOURCES_FOLDER_PATH)/GoogleService-Info.plist\n ``` \n\n ```\n $(TARGET_BUILD_DIR)/$(EXECUTABLE_PATH)\n ```\n If you have `ENABLE_USER_SCRIPT_SANDBOXING=YES` and `ENABLE_DEBUG_DYLIB=YES` in your project build settings, then include the following: \n\n ```\n ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${PRODUCT_NAME}.debug.dylib\n ```\n **Understand why the locations of these files are\n needed**\n\n Xcode looks in the specified locations for these input files to ensure\n that the build files are available for the run script. Also, if\n *User Script Sandboxing* is enabled, Xcode only allows the run\n script to access files specified in the *Input Files*.\n - Providing the location of your project's dSYM files enables Crashlytics to process dSYMs.\n - Providing the location of your app's built `GoogleService-Info.plist` file enables Crashlytics to associate the dSYMs with your Firebase app.\n - Providing the location of your app's executable allows the run script to prevent duplicate uploads of the same dSYM. Note that app binaries are *not uploaded*.\n\nCheck if Xcode is producing dSYMs\n\nMore often than not, dSYM files go missing because Xcode simply isn't producing\nthem. When an upload fails, Crashlytics displays a \"Missing dSYM\" alert in\nthe Firebase console. If you get this alert, first check that Xcode is\nproducing the correct dSYM for every build:\n\n1. Open your project in Xcode, and then select the project file in the Xcode\n Navigator.\n\n2. Select your main build target.\n\n3. Open the target's **Build Settings** tab, and then click **All**.\n\n4. Search for `debug information format`.\n\n5. Set **Debug Information Format** to **DWARF with dSYM File** for all\n your build types.\n\n6. Rebuild your app.\n\nYour crash reports should now appear in the\n[Crashlytics dashboard](https://console.firebase.google.com/project/_/crashlytics). If the problem persists or you\nencounter other errors, try [locating your dSYMs](#locate) and\n[uploading them to Crashlytics manually](#upload-dsyms).\n\nLocate your dSYMs on a local machine\n\nRun the following command to display all your dSYMs' UUIDs on your machine and\nsearch for the missing dSYM: \n\n```text\nmdfind -name .dSYM | while read -r line; do dwarfdump -u \"$line\"; done\n```\n\nOnce you find the dSYM, [manually upload it to Crashlytics](#upload-dsyms).\nIf the `mdfind` command doesn't return any results, you can look in the\n`Products` directory where your `.app` lives (by default, the `Products`\ndirectory is located in `Derived Data`). If your app is released to production,\nyou can also look for its dSYM in the `.xcarchive` directory on disk:\n\n1. In Xcode, open the **Organizer** window, and then select your app from the\n list. Xcode displays a list of archives for your project.\n\n2. Control-click an archive to view it in Finder. Control-click it again, and\n then click **Show Package Contents**.\n\n3. Within `.xcarchive` is a dSYMs directory that contains dSYMs generated as\n part of Xcode's archiving process.\n\nUpload your dSYMs\n\nCrashlytics supports multiple ways to upload your dSYMs files, either\n[automatically](#auto-upload-dsyms) or [manually](#manually-upload-dsyms).\n\n*(Recommended)* Automatically process your dSYMs and upload the files\n\nWhen you initially set up Crashlytics, you most likely configured this\nautomatic upload behavior for your app. However, if automatic uploads are\nfailing, [check that your configuration is correct](#check-input-files-setup).\n\nManually upload your dSYM files\n\nIf automatic uploads are failing, you can manually upload your dSYM files using\neither of the following options.\n\n- **Option 1** : Use the console-based \"Drag and Drop\" option to upload a zip\n file containing your dSYM files (go to the\n Firebase console \\\u003e\n [Crashlytics](https://console.firebase.google.com/project/_/crashlytics) \\\u003e\n *dSYMs* tab).\n\n- **Option 2** : Use the `upload-symbols` script that you can call from\n anywhere in your build process to manually upload your dSYM files. To run the\n `upload-symbols` script, use either of the following options:\n\n - **Option A**: Include the following line in your build process:\n\n ```gdscript\n find dSYM_DIRECTORY -name \"*.dSYM\" | xargs -I \\{\\} $PODS_ROOT/FirebaseCrashlytics/upload-symbols -gsp /PATH/TO/GoogleService-Info.plist -p PLATFORM \\{\\}\n ```\n - **Option B**: Run the script directly from your terminal:\n\n ```\n /PATH/TO/PODS/DIRECTORY/FirebaseCrashlytics/upload-symbols -gsp /PATH/TO/GoogleService-Info.plist -p ios /PATH/TO/dSYMs\n ```\n\n For usage notes and additional instructions about this script, run\n `upload-symbols` with the `--help` parameter."]]