Accesses the singleton Crashlytics instance.

Adds logging that is sent with your crash data. The logging does not appear in app logs and is only visible in the Crashlytics dashboard.

Adds logging that is sent with your crash data. The logging does not appear in app logs and is only visible in the Crashlytics dashboard.

Adds logging that is sent with your crash data. The logging does not appear in app logs and is only visible in the Crashlytics dashboard.

Sets a custom key and value to be associated with subsequent fatal and non-fatal reports. When setting an object value, the object is converted to a string. This is typically done by using the object’s description.

Sets custom keys and values to be associated with subsequent fatal and non-fatal reports. The objects in the dictionary are converted to strings. This is typically done by using the object’s description.

Records a user ID (identifier) that’s associated with subsequent fatal and non-fatal reports.

If you want to associate a crash with a specific user, we recommend specifying an arbitrary string (e.g., a database, ID, hash, or other value that you can index and query, but is meaningless to a third-party observer). This allows you to facilitate responses for support requests and reach out to users for more information.

Records a non-fatal event described by an Error object. The events are grouped and displayed similarly to crashes. Keep in mind that this method can be expensive. The total number of Errors that can be recorded during your app’s life-cycle is limited by a fixed-size circular buffer. If the buffer is overrun, the oldest data is dropped. Errors are relayed to Crashlytics on a subsequent launch of your application.

Records a non-fatal event described by an NSError object. The events are grouped and displayed similarly to crashes. Keep in mind that this method can be expensive. The total number of NSErrors that can be recorded during your app’s life-cycle is limited by a fixed-size circular buffer. If the buffer is overrun, the oldest data is dropped. Errors are relayed to Crashlytics on a subsequent launch of your application.

Records an Exception Model described by an ExceptionModel object. The events are grouped and displayed similarly to crashes. Keep in mind that this method can be expensive. The total number of ExceptionModels that can be recorded during your app’s life-cycle is limited by a fixed-size circular buffer. If the buffer is overrun, the oldest data is dropped. ExceptionModels are relayed to Crashlytics on a subsequent launch of your application.

Returns whether the app crashed during the previous execution.

Enables/disables automatic data collection.

Calling this method overrides both the FirebaseCrashlyticsCollectionEnabled flag in your App’s Info.plist and FirebaseApp’s isDataCollectionDefaultEnabled flag.

When you set a value for this method, it persists across runs of the app.

The value does not apply until the next run of the app. If you want to disable data collection without rebooting, add the FirebaseCrashlyticsCollectionEnabled flag to your app’s Info.plist. *

Indicates whether or not automatic data collection is enabled

This method uses three ways to decide whether automatic data collection is enabled, in order of priority:

• If setCrashlyticsCollectionEnabled is called with a value, use it
• If the FirebaseCrashlyticsCollectionEnabled key is in your app’s Info.plist, use it
• Otherwise, use the default isDataCollectionDefaultEnabled in FirebaseApp

Determines whether there are any unsent crash reports cached on the device, then calls the given callback.

The callback only executes if automatic data collection is disabled. You can use the callback to get one-time consent from a user upon a crash, and then call sendUnsentReports or deleteUnsentReports, depending on whether or not the user gives consent.

Disable automatic collection by:

• Adding the FirebaseCrashlyticsCollectionEnabled key with the value set to NO to your app’s Info.plist
• Calling FirebaseCrashlytics.crashlytics().setCrashlyticsCollectionEnabled(false) in your app

• Setting FirebaseApp‘s isDataCollectionDefaultEnabled to false

Determines whether there are any unsent crash reports cached on the device, then calls the given callback with a CrashlyticsReport object that you can use to update the unsent report. CrashlyticsReports have a lot of the familiar Crashlytics methods like setting custom keys and logs.

The callback only executes if automatic data collection is disabled. You can use the callback to get one-time consent from a user upon a crash, and then call sendUnsentReports or deleteUnsentReports, depending on whether or not the user gives consent.

Disable automatic collection by:

• Adding the FirebaseCrashlyticsCollectionEnabled key with the value set to NO to your app’s Info.plist
• Calling FirebaseCrashlytics.crashlytics().setCrashlyticsCollectionEnabled(false) in your app
• Setting FirebaseApp‘s isDataCollectionDefaultEnabled to false

Not calling sendUnsentReports()/deleteUnsentReports() will result in the report staying on disk, which means the same CrashlyticsReport can show up in multiple runs of the app. If you want avoid duplicates, ensure there was a crash on the last run of the app by checking the value of didCrashDuringPreviousExecution.

Enqueues any unsent reports on the device to upload to Crashlytics.

This method only applies if automatic data collection is disabled.

When automatic data collection is enabled, Crashlytics automatically uploads and deletes reports at startup, so this method is ignored.

Deletes any unsent reports on the device.

This method only applies if automatic data collection is disabled.