Reputation: 1352
I implemented Firebase Crashlytics in my iOS app. I followed all the steps in firebase documentation. I already ran crashlytics without the debugger by closing the app first and then re run the app so that crash reports can be sent. I even get this message
Crash upload submission succesful
I even added the Run script and set variable to "DWARF with DSYM"
"${PODS_ROOT}/Fabric/run"
I ready somewhere that if DSYM aren't uploaded you won't see your crashes even if they are uploaded successfully. So I went into my pods/Fabric/ and click on "run" CLI. It clearly says DSYM not uploaded because GoogleServiceInfo.plist wasn't found. Although it's there and yes it's included in my target as well as in my bundle.
Here is the screenshot. I have tried all possible steps to include GoogleService-Info.plist but still when I run manually it says this.
Any another thing that I can try ?
Upvotes: 21
Views: 31455
Reputation: 9226
I have tried several things but only below steps worked for me:
FirebaseApp.configure()
to the first line of didFinishLaunchingWithOptions
Firebase/Crashlytics
and Crashlytics
, remove Crashlytics
from pods and update itRun Script
in Build Phases. If you have entry for "${PODS_ROOT}/FirebaseCrashlytics/run"
.-FIRDebugEnabled
in Project's test scheme.Upvotes: 14
Reputation: 88
If anyone follows the example here https://capawesome.io/plugins/firebase/crashlytics/ and still doesn't see crashes show up, try adding these lines to your Build Phases
-> Run script
-> Input Files
section
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Info.plist
$(TARGET_BUILD_DIR)/$(UNLOCALIZED_RESOURCES_FOLDER_PATH)/GoogleService-Info.plist
After adding these two lines all my crashes started coming in.
Upvotes: 0
Reputation: 173
For SwiftUI and Swift 5 paste below code to under of Buid Phases
Script:
"${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run"
Upvotes: 0
Reputation: 1125
After following all the necessary steps: NOT running the app from Xcode, but from iPhone/simulator interface helped me detect the crash in Crashlytics dashboard.
Upvotes: 0
Reputation: 16032
I solving the same issue adding the FirebaseCraslytics
pod to my Podfile
:
...
pod 'FirebaseAnalytics'
pod 'FirebaseCrashlytics'
Then I added the following Run Script
in the Build Phases
:
Script:
"${PODS_ROOT}/FirebaseCrashlytics/run"
Input Files:
$(SRCROOT)/$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)
$(SRCROOT)/${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TARGET_NAME}
After that, I followed the Step 3: Force a test crash to finish setup and Crashlytics
start to working.
Upvotes: 0
Reputation: 811
After following all the steps as stated in the docs followed below steps:
They starting showing on the console.
Upvotes: 6
Reputation: 558
Try this:
For reference:
Integrating Firebase and Crashlytics in iOS
Upvotes: 42
Reputation: 3791
When I have this issue, I do a manual install and yes first use the Fabric app to initialise the app into their system - https://fabric.io/kits/ios/crashlytics/manual-install
Upvotes: -4
Reputation: 1352
To someone still struggling with the issue here is what resolved the issue for me.
I deleted the GoogleService-Info.plist and added it again.
I tried the crash on my welcome screen rather than in one of the screens of my tab bar controller as I believe from there it's unable to find GoogleServiceInfo.plist file so it worked.
Upvotes: 7