elenadoty bb8965c3ce Upload fatal MK reports on the next run of the app (#8688) 4 yıl önce
..
Crashlytics bb8965c3ce Upload fatal MK reports on the next run of the app (#8688) 4 yıl önce
ProtoSupport 41020e6d78 Bump the nanopb version to 0.3.9.8 (#7789) 5 yıl önce
Protogen 4424e9a5d3 Bump nanopb to 0.3.9.7 (#7108) 5 yıl önce
Shared 0d90f2f12d Update to clang-format 12.0.1 (#8397) 4 yıl önce
UnitTests c483477667 Fix compiler checks for xcode 13 (#8679) 4 yıl önce
third_party 3dc11858ff Open Sourcing FirebaseCrashlytics (#4610) 6 yıl önce
CHANGELOG.md b08b358ca3 Prepare for Firebase 8.8 release (#8686) 4 yıl önce
LICENSE 41b46131a1 Crashlytics update LICENSE file for libunwind (#4657) 6 yıl önce
README.md db3ace1bbd Update README.md for updating crash report uploads (#5207) 6 yıl önce
generate_project.sh bab9af811f Remove watchOS for Crashlytics Pod Gen (#7372) 5 yıl önce
run 616067635b Crashlytics update run script to quote all arguments passed (#6789) 5 yıl önce
upload-symbols bc7ccd55c5 Update upload symbols tool logs (#8144) 4 yıl önce

README.md

Firebase Crashlytics SDK

Development

Follow the subsequent instructions to develop, debug, unit test, and integration test FirebaseCrashlytics:

Prereqs

  • At least CocoaPods 1.6.0
  • Install cocoapods-generate
  • For nanopb and GDT:
    • brew install protobuf nanopb-generator
    • easy_install protobuf python

To Develop

  • Run Crashlytics/generate_project.sh
  • open gen/FirebaseCrashlytics/FirebaseCrashlytics.xcworkspace

You're now in an Xcode workspace generate for building, debugging and testing the FirebaseCrashlytics CocoaPod.

Running Unit Tests

Open the generated workspace, choose the FirebaseCrashlytics-Unit-unit scheme and press Command-u.

Changing crash report uploads (using GDT)

Update report proto

If the crash report proto needs to be updated, follow these instructions:

  • Update ProtoSupport/Protos/crashlytics.proto with the new changes
  • Depending on the type of fields added/removed, also update ProtoSupport/Protos/crashlytics.options. CALLBACK type fields in crashlytics.nanopb.c needs to be changed to POINTER (through the options file). Known field types that require an entry in crashlytics.options are strings, repeated and bytes.
  • Run generate_project.sh to update the nanopb .c/.h files.