Splunk Search

Why am I getting "Incoming data was invalid...Keys missing: {(name, transactionId)}" after updating from BugSense to Splunk?

ljfantin
Engager

Hi Guys,
I updated from BugSense to Splunk and I saw this in my log

[SPLJSONModel.m:256] Incoming data was invalid [TrStart initWithDictionary:]. Keys missing: {(
name,
transactionId
)}

Can anyone help me?

Thanks

1 Solution

gtaskos_splunk
Splunk Employee
Splunk Employee

Hi,

This is an internal message and it will be disabled in the next release of the SDK.
It doesn't affect the flow of the application and it is not an error, actually is a message just for validating JSON fixture converted to object instance and is there for our purpose.

Please find in the following link the latest release build with this change. http://1drv.ms/1vnO8qK.

Thank you for your feedback and for using Splunk MINT.

View solution in original post

ethanwa
New Member

Hi, one of my devs was getting this error over and over in a loop and his iPhone Simulator crashed with out of memory errors. His log was FULL of these. The only way we could get the looping of this [SPLJSONModel.m:256] Incoming data was invalid [TrStart initWithDictionary:]. Keys missing: error to stop was to reset his simulator completely and reinstall our app. Now it shows up 5-25 times on every load.

I hope this doesn't end up happening live.

0 Karma

gtaskos_splunk
Splunk Employee
Splunk Employee

This logging message was only appeared when using the iOS simulator and it was for debugging purposes. It is already removed and you will not experience it anymore. Find the latest release build in the following link, http://1drv.ms/1vnO8qK, if you want an early use of the upcoming release.

0 Karma

gtaskos_splunk
Splunk Employee
Splunk Employee

Hi,

This is an internal message and it will be disabled in the next release of the SDK.
It doesn't affect the flow of the application and it is not an error, actually is a message just for validating JSON fixture converted to object instance and is there for our purpose.

Please find in the following link the latest release build with this change. http://1drv.ms/1vnO8qK.

Thank you for your feedback and for using Splunk MINT.

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...