Splunk MINT: How do we prevent our app from crashing when the Splunk Java SDK throws an exception?

[neerajjindal201]

We had a recent scenario where Splunk was throwing a null pointer exception and it caused our app to crash. This happened only on September 9 (after months of testing on our side and no changes to our Splunk calls). We had many many crashes and subsequent bad reviews. The crashes stopped occurring after something (again) changed on the Splunk server.

Here is a stack trace:

java.lang.NullPointerException
at com.splunk.mint.RemoteSettings.convertJsonToRemoteSettings(SourceFile:38)
at com.splunk.mint.ActionEvent.send(SourceFile:93)
at com.splunk.mint.Mint$2.run(SourceFile:183)
at java.lang.Thread.run(Thread.java:856)

Other than making sure using the latest version of the SDK, we want to add something in our code that catches all exceptions from the SDK so we don't get bad reviews in and when the Splunk server has a problem.

How do we do this?
Meaning, is there something we can override, put a try catch around or...whatever you recommend so we don't get crashes from you?

[croyal_splunk]

The September 2015 issue lasted approximately 3 hours. We're sorry for the negative impact. The team did add additional safeguards and we do not expect similar issues in the future.

You can track Known Issues for iOS and Android SDKs.