Discussion

This is useful if you are e.g. distributing an enterprise app inside your company and want to use the liveIdentifier for that even though it is not running from the App Store.

Example:

 - (BOOL)shouldUseLiveIdentifierForHockeyManager:(BITHockeyManager *)hockeyManager {
 #ifdef (CONFIGURATION_AppStore)
   return YES;
 #endif
   return NO;
 }

Discussion

Right now this is used by the BITCrashManager to attach to a crash report. BITFeedbackManager uses it too for assigning the user to a discussion thread.

In addition, if this returns not nil for BITFeedbackManager the user will not be asked for any user details by the component, including useerName or userEmail.

You can find out the component requesting the user email like this:

- (NSString *)userEmailForHockeyManager:(BITHockeyManager *)hockeyManager componentManager:(BITHockeyBaseManager *)componentManager {
  if (componentManager == hockeyManager.feedbackManager) {
    return UserEmailForFeedback;
  } else if (componentManager == hockeyManager.crashManager) {
    return UserEmailForCrashReports;
   } else {
    return nil;
   }
}

For crash reports, this delegate is invoked on the startup after the crash!

Alternatively you can also use [BITHockeyManager userEmail] which will cache the value in the keychain.

Discussion

Right now this is used by the BITCrashManager to attach to a crash report. BITFeedbackManager uses it too for assigning the user to a discussion thread.

In addition, if this returns not nil for BITFeedbackManager the user will not be asked for any user details by the component, including useerName or userEmail.

You can find out the component requesting the userID like this:

- (NSString *)userIDForHockeyManager:(BITHockeyManager *)hockeyManager componentManager:(BITHockeyBaseManager *)componentManager {
  if (componentManager == hockeyManager.feedbackManager) {
    return UserIDForFeedback;
  } else if (componentManager == hockeyManager.crashManager) {
    return UserIDForCrashReports;
  } else {
    return nil;
  }
}

For crash reports, this delegate is invoked on the startup after the crash!

Alternatively you can also use [BITHockeyManager userID] which will cache the value in the keychain.

Discussion

Right now this is used by the BITCrashManager to attach to a crash report. BITFeedbackManager uses it too for assigning the user to a discussion thread.

In addition, if this returns not nil for BITFeedbackManager the user will not be asked for any user details by the component, including useerName or userEmail.

You can find out the component requesting the user name like this:

- (NSString *)userNameForHockeyManager:(BITHockeyManager *)hockeyManager componentManager:(BITHockeyBaseManager *)componentManager {
  if (componentManager == hockeyManager.feedbackManager) {
    return UserNameForFeedback;
  } else if (componentManager == hockeyManager.crashManager) {
    return UserNameForCrashReports;
  } else {
    return nil;
  }

}

For crash reports, this delegate is invoked on the startup after the crash!

Alternatively you can also use [BITHockeyManager userName] which will cache the value in the keychain.

Discussion

By default the SDK is using the root UIWindow instance to present any required view controllers. Overwrite this if this doesn’t result in a satisfying behavior or if you want to define any other parent view controller.