At times, even full stack traces with line numbers aren't quite enough to pinpoint the bug. To give you even more insight, Crashlytics provides 3 logging mechanisms right out of the box, Custom Logging, Custom Keys, and User Information.
In order to better respond to customer support inquiries, it's often helpful to know which of your users experienced a given crash. Fortunately, Crashlytics makes this easy!
You can use
[Crashlytics setUserIdentifier:] to provide an id number, token, or hashed value that uniquely identifies the end-user of your application without disclosing or transmitting any of their personal information. You can also clear the value by setting it to a blank string. This value is displayed right in the Crashlytics dashboard.
+ (void)setUserIdentifier:(NSString *)identifier;
If you would like to take advantage of advanced user identifier features, you can additionally use both:
+ (void)setUserName:(NSString *)name;
+ (void)setUserEmail:(NSString *)email;
Be sure you set these after calling Crashlytics startWithAPIKey!
You can also search on these as well :-)
For developers that want to take full advantage of our user feature set, setting all three is recommended.
Thread safe as of SDK version 1.1.6.