Reputation: 23
For my app, I tried to configure the Firebase Crashlytics. For configuring I’m not using the pod file. Installed Firebase Without Using CocoaPods. For that I followed the following link: https://mokacoding.com/blog/setting-up-firebase-without-cocoapods/
Then I added GoogleService-Info.plist to the project from the Firebase account.
After that, I changed the DEBUG_INFORMATION_FORMAT from DWARF to dwarf-with-dsym in Build options. Then I added the Run script in the Build phase.
Added the following script: "${PROJECT_DIR}/ProjectName/GoogleService-Info.plist" -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}"
For install build only selected Based on the dependency analysis is selected
Then in input files, I added the following:
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TARGET_NAME}
$(SRCROOT)/$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)
Changed the Scheme from debug to release.
I could not able to get the crash from crashlytics console. Is any issue is with the run scrips? I appreciate your help in advance.
Upvotes: 0
Views: 740
Reputation: 187
These configurations are not directly related to Crashlytics' crash report operation. These are used to send desymbollers to Firebase. So Firebase can desymbol your crash info and provide you a readable crash report. So, I am not sure that a failure in these configurations can cause your problem. As I know, if you have a failure in these steps; After your app crash, you need to see "Missing dsymbols" error on Firebase Crashlytics panel
If you cannot see your crash report, you need to check steps to integrate crashlytics properly. And maybe enable Firebase debug mode and check logs.
By the way, Crashlytics' first integration steps may be annoying. You may need to read and apply these steps carefully. Especially test crash step.
Upvotes: 1