Nhận báo cáo sự cố có thể đọc được trên trang tổng quan Crashlytics
Sử dụng bộ sưu tập để sắp xếp ngăn nắp các trang
Lưu và phân loại nội dung dựa trên lựa chọn ưu tiên của bạn.
Trình bổ trợ Crashlytics Gradle có thể tự động phát hiện thời điểm bạn làm rối mã nguồn. Khi bản dựng của bạn tạo một tệp ánh xạ, trình bổ trợ sẽ tải tệp đó lên để các máy chủ Crashlytics có thể dùng tệp này để hiển thị dấu vết ngăn xếp của ứng dụng dưới dạng mã không bị làm rối và dễ đọc.
Cấu hình bắt buộc khi sử dụng R8, ProGuard và DexGuard
Crashlytics có thể gỡ rối bằng mọi tệp ánh xạ tương thích với ProGuard và đã được kiểm thử thêm bằng ProGuard, R8 và DexGuard.
Nếu ứng dụng của bạn sử dụng R8 khi bật tính năng làm rối mã cùng với Android Gradle 4.2.0 trở lên, thì Crashlytics sẽ tạo ra các báo cáo sự cố dễ đọc. Xin lưu ý rằng Crashlytics gần đây đã cải thiện khả năng hỗ trợ cho các ứng dụng sử dụng cả Kotlin và R8, điều này có thể dẫn đến một số vấn đề gắn nhãn không mong muốn.
Nếu ứng dụng của bạn sử dụng tệp cấu hình ProGuard, bạn cần phải giữ lại thông tin mà Crashlytics yêu cầu để tạo báo cáo sự cố dễ đọc. Hãy thực hiện việc này bằng cách thêm các dòng sau vào tệp cấu hình ProGuard hoặc DexGuard:
-keepattributesSourceFile,LineNumberTable# Keep file names and line numbers.-keeppublicclass*extendsjava.lang.Exception# Optional: Keep custom exceptions.
Để ngăn trình bổ trợ Gradle Crashlytics tải tệp ánh xạ lên cho các biến thể sử dụng phương pháp làm rối mã nguồn, hãy đặt thuộc tính tiện ích firebaseCrashlytics.mappingFileUploadEnabled Gradle thành false trong tệp Gradle mô-đun (cấp ứng dụng) (thường là <project>/<app-module>/build.gradle.kts hoặc <project>/<app-module>/build.gradle). Việc này có thể giúp tăng tốc thời gian tạo cho các bản dựng bị làm rối mã nguồn, nhưng lưu ý rằng các dấu vết ngăn xếp thu được sẽ xuất hiện dưới dạng bị làm rối mã nguồn trong trang Crashlytics của bảng điều khiển Firebase.
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,["Cập nhật lần gần đây nhất: 2025-08-11 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."]]
