Paul Beusterien e15724a436 Migrate from interop pods to source_files header access (#5760) 5 rokov pred
..
Crashlytics e15724a436 Migrate from interop pods to source_files header access (#5760) 5 rokov pred
ProtoSupport 8e1be65b2f Verifies nanopb 0.3.9.5 update does not change generation (#5455) 6 rokov pred
Protogen 8e1be65b2f Verifies nanopb 0.3.9.5 update does not change generation (#5455) 6 rokov pred
Shared 30f2d66ea1 Crashlytics/issues/5020 (#5414) 6 rokov pred
UnitTests d4621a636f Use preserve_paths instead of CocoaPods private (#5758) 5 rokov pred
third_party 3dc11858ff Open Sourcing FirebaseCrashlytics (#4610) 6 rokov pred
CHANGELOG.md a20199b325 Update changelogs for M72 (#5714) 5 rokov pred
LICENSE 41b46131a1 Crashlytics update LICENSE file for libunwind (#4657) 6 rokov pred
README.md db3ace1bbd Update README.md for updating crash report uploads (#5207) 6 rokov pred
generate_project.sh 194439fdfb Integrating GoogleDataTransport in Crashlytics to Report Crashes (#4989) 6 rokov pred
run 3dc11858ff Open Sourcing FirebaseCrashlytics (#4610) 6 rokov pred
upload-symbols 53e71073d8 Merge upload-symbols version 3.3 (#5228) 6 rokov pred

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.