Reporting

Splunk MINT SDK crash

KlausPed
New Member

Hi 

I'm using this guide for Splunk MINT and I'm using the SAP SDK also

https://docs.splunk.com/Documentation/MintIOSSDK/5.2.x/DevGuide/Requirementsandinstallation

And I have done the following

 - Downloading the sdk, and adding the framework and other required frameworks 

- Made the setting in the app, but not configured server side for symbolication

 - Init the Mint SDK with the API_KEY from my account 

But my app crash with the following error in the console:

Main Thread Checker: UI API called on a background thread: -[UIApplication keyWindow]

PID: 69771, TID: 5607271, Thread name: (none), Queue name: com.splunk.MINT.SequentialOperations, QoS: 0

Backtrace:

4   My Time QA                          0x000000010778d259 -[ScreenMonitorManager init] + 131

5   My Time QA                          0x000000010778d1b0 __38+[ScreenMonitorManager sharedInstance]_block_invoke + 38

6   libdispatch.dylib                   0x0000000111fafdb5 _dispatch_client_callout + 8

7   libdispatch.dylib                   0x0000000111fb183c _dispatch_once_callout + 66

8   My Time QA                          0x000000010778d188 +[ScreenMonitorManager sharedInstance] + 102

9   My Time QA                          0x000000010776dc99 -[DataFixture appendBaseValues] + 1316

10  My Time QA                          0x000000010776d76b -[DataFixture init] + 64

11  My Time QA                          0x0000000107796d71 -[EventDataFixture init] + 46

12  My Time QA                          0x000000010776e9ce +[PingDataFixture getInstanceWithDeviceStatus:] + 41

13  My Time QA                          0x000000010779f5a5 -[MintRequestJsonSerializer serializeEventToJsonForPingWithDeviceStatus:] + 70

14  My Time QA                          0x0000000107775783 __46-[MintRequestWorker sendPing:completionBlock:]_block_invoke + 520

15  libdispatch.dylib                   0x0000000111faed7f _dispatch_call_block_and_release + 12

16  libdispatch.dylib                   0x0000000111fafdb5 _dispatch_client_callout + 8

17  libdispatch.dylib                   0x0000000111fb7225 _dispatch_lane_serial_drain + 778

18  libdispatch.dylib                   0x0000000111fb7e9c _dispatch_lane_invoke + 425

19  libdispatch.dylib                   0x0000000111fc1ea3 _dispatch_workloop_worker_thread + 733

20  libsystem_pthread.dylib             0x0000000112466a3d _pthread_wqthread + 290

21  libsystem_pthread.dylib             0x0000000112465b77 start_wqthread + 15

Best Regards

Klaus

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...