Do we need to remove fabric after migrating the firebase in iOS swift?

user_5368793 0
Viewed 314

While creating a new project using pod FirebaseCrashlytics, I am able to get new crashes and the existing crash count also increases when same crashes occur.

pod 'FirebaseCrashlytics', '4.5.0'
pod 'FirebaseAnalytics', '6.8.0'
pod 'FirebaseCore', '6.10.1'
pod 'FirebaseMessaging', '4.6.2'

For initializing the crashlytics I have added the script in the build phases:

"${PODS_ROOT}/FirebaseCrashlytics/run" Input Files:


${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TARGET_NAME} $(SRCROOT)/$(BUILT_PRODUCTS_DIR)/$(INFOPLIST_PATH)

NOTE:

  1. While forcing a crash in the existing project that we migrated from Fabric to Firebase, the crashlytics are not logged, if we removed the fabric functionalities from the plist/build phase and entire code and followed the above steps.

  2. While forcing a crash in the existing project that we migrated from Fabric to Firebase, the crashlytics are logged, if we are not removing the fabric functionalities from the plist/build phase and entire code and followed the above steps.

Is there any additional settings that need to be done so that the crashes are logged in the migrated project itself?

crashlytics firebase swift ios
1 Answers

If you have migrated your app from Fabric, you cannot simply delete your Fabric API key and Fabric dependencies, this will cause issues for your app. Make sure you follow this guide entirely for your migrated app, and it should resolve any of your crash reporting issues.

user_119531000
Related