🚧

Privacy Policy

It is highly recommended to mention in your privacy policy that you may be collecting logging data in order to assist with troubleshooting crashes.

There are two ways to have your application report a crash, either automatically or manually. After the crash is sent to your dashboard, you can sort and filter for specific crashes easily.

Automatic Crash Reporting

If your plan includes crash reporting, crashes will automatically be reported to and viewable from the crashes page of your Instabug dashboard.

🚧

Warning

Crash reporting will not function correctly if the device is connected to Xcode. When it is, Xcode catches all the exceptions and they are not sent to your dashboard.

Manual Crash Reporting

You can manually report your own exceptions or errors in case you already handle them in your code.

Report Exception

To report exceptions manually, use the following method.

CrashReporting.report(exception)

[IBGCrashReporting reportException:exception];

Report Errors

To report errors manually, use the following method.

let error = NSError(domain: "domain", code: 500, userInfo: nil)
CrashReporting.reportError(error)

NSError *error = [[NSError alloc] initWithDomain:@"domain" code:500 userInfo:nil];
[IBGCrashReporting reportError:error];

Crashes List

This section contains a list of all the crashes that have been reported by your application. The title of each crash is usually the most significant line in the stack trace.

Next to each crash in the list, you can find the following details, all of which can be used to sort the crashes:

• Severity: Blue dashes that show the seriousness of this crash from low (one dash), moderate (two dashes), high (three dashes), and critical (four dashes) by taking into consideration the frequency of the crash, the number of affected users, and the recency of its occurrence.
• Occurrences: The number of times this crash has occurred.
• Users: The number of users affected by this crash.
• Min Version: The lowest app version number affected by this crash.
• Max Version: The highest app version number affected by this crash.
• Last Occurred: When the latest occurrence of this crash happened.

You can then filter for crashes that match any of the following criteria:

• Status
• Assignee
• Priority
• Severity
• App Version
• OS
• Type
• Integrations
• User Attributes