I didn't touch my app for more then a year, and all of a sudden I get
0java.lang.NullPointerException: Attempt to get length of null array
1 at com.splunk.mint.DataFlusher$1.run(SourceFile:30)
2 at java.lang.Thread.run(Thread.java:818)
3 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
4 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
5 at java.lang.Thread.run(Thread.java:818)
If I look deeper, I see that it is accompanied by another exception I threw, because of a view remained null after the init.
Now I'm not too familiar with SplunkMINT but I suspect this is actually an issue with the Android app that you are using. As you mentioned that you haven't used this app in over a year I would first make sure that your app is up to date as the developer may have fixed the issue in the meantime. If the issue is still present, I would then contact the developer of said app to report the issue to them. I suspect this is a bug in how the developer is using the MINT SDK, as I found a GitHub Issue on another developer's repository. That developer seems to have fixed this issue by updating the version of the MINT SDK that they were using and ensuring that they were not attempting to set a null object somewhere.
GitHub Issue: https://github.com/domoticz/domoticz-android/issues/262
Related Commit: https://github.com/domoticz/domoticz-android/commit/f3a5713a5d00cbbe492c269b63e3510632b42d1c
Oh so you saw this bug on answers.splunk.com
So look here https://answers.splunk.com/answers/216856/how-do-i-file-a-splunk-support-case
Maybe email to support@splunk.com
Seems like it was an intermittent bug unless you can reproduce the bug.
You haven't given us enough context to understand what your issue is, let alone to help you resolve it.
What app? What version? What version of splunk are you on? What operating system? What were you doing when the app threw the error? If you haven't touched the app for a year, what establishes that it should have been working before today? (ie, How do we know it didn't break six months ago?)
Hi. What are you running exactly that gets you this error?
Android 6.1
The bug was reported on your site... It didn't happen to me.
IDK - I didn't run it - the error was reported to me on your site.