how to get the id (or Splunk URL) of the last crash, on iOS (migrating from BugSense)

[dan_morrow]

I'm currently a BugSense user, migrating to the new Splunk APIs. Here's what I'm trying to accomplish:

1. User relaunches the app after a crash.
2. The user is presented with "Hey, it looks like you just crashed, could you tell us about it?"
3. The user enters some information about it, and it gets sent to our server, with the BugSense URL that has the crash-report.

In the old BugSense APIs, we'd do something like this:

[BugSenseController setErrorNetworkOperationsCompletionBlock:^() {
  if ([BugSenseController crashCount] == 1) { // a crash occurred on last run
   long lastCrashID = [BugSenseController lastCrashId];
   NSString *bugURL = [NSString stringWithFormat:@"https://www.bugsense.com/dashboard/project/%@/errors/%ld", myAPIKey, lastCrashID];

   [self askUserForMoreInfoWithCrashURL:bugURL]; // ask user for more info.
   [BugSenseController resetCrashCount]
  }
}

If the user filled out the form, his input and the BugSense URL would get sent to our servers, and we could then bring up the crash-report at a later date.

I'm having trouble finding the definitive way to do this. I see some things which look like they might help ,but unsure how to proceed.

Thanks in advance for any help.

[ppapadopoulos_s]

Hi Dan, unfortunately this feature is not supported in the new Splunk MINT SDKs. It has been deprecated as we have switched to fully async requests and batching.

[richgalloway]

How are you replacing BugSense with Splunk? Splunk doesn't seem to fit the use case you describe, except as the recipient of "it gets sent to our server". Once the bug report is completed, sent to Splunk, and indexed you use the Splunk API to bring up the crash report.

[dan_morrow]

Maybe I should've been more specific, I'm using SplunkMINT on iOS, and it does fit the use-case nicely. The new SplunkMINT kit for iOS sends crash-reports to Splunk, just as the old BugSense did.

All I want to do is know is when a crash-report got sent to Splunk, so I can get the URL, and reference it later. The way I did it worked as described in my original post. In my case, I'm allowing the user to add some extra data, so I get a better feel about what's going on. And I can also send them a note back, asking for more information. Or I can tell them to look forward to a bug-fix release soon, etc.

[richgalloway]

Thanks for the clarification. I'm a Splunk Enterprise user with no SplunkMINT experience so I can't help you. Sorry.