Connect IQ

Connect IQ App Development Discussion Background processes cannot modify the object store native function

Background processes cannot modify the object store native function

GHG23 over 8 years ago

My new datafield that I am building has a few early bird users and one of them keeps getting crashes. I have really no idea what this error means, looking at the CIQ_LOG.TXT. My datafield doesn't use local storage, it only takes settings from the property. Like : sAveragePaceSec = mApp.getProperty("pAveragePaceSec");

The Log file (based on a normal version of the datafield, not a special debug version):
"Background processes cannot modify the object store
native function

ERROR: Unhandled Exception
DETAILS: NONE
STORE_ID: 6b9d2d26d7464377830e83422e3df45b
CALLSTACK:
Background processes cannot modify the object store
native function

ERROR: Unhandled Exception
DETAILS: NONE
STORE_ID: 6b9d2d26d7464377830e83422e3df45b
CALLSTACK:
Background processes cannot modify the object store
native function

ERROR: Unhandled Exception
DETAILS: NONE
STORE_ID: 6b9d2d26d7464377830e83422e3df45b
CALLSTACK:
Background processes cannot modify the object store
native function

"

Top Replies

Former Member over 8 years ago +1

That exception is thrown if any of these methods are called from a background process:

Application.AppBase.setProperty()
Application.AppBase.deleteProperty()
Application.AppBase.clearProperties()

Application…

All Replies

jim_m_58 over 8 years ago

Are you ever doing a setProperty in the background? You can't do that for the setting or the Object store in the background. Same with setValue for Application.Storage or Application.Properties

Former Member over 8 years ago

That exception is thrown if any of these methods are called from a background process:

Application.AppBase.setProperty()
Application.AppBase.deleteProperty()
Application.AppBase.clearProperties()

Application.Storage.SetValue()
Application.Storage.deleteValue()
Application.Storage.clearValues()

Application.Properties.setValue()

GHG23 over 8 years ago

That exception is thrown if any of these methods are called from a background process:

Application.AppBase.setProperty()
Application.AppBase.deleteProperty()
Application.AppBase.clearProperties()

Application.Storage.SetValue()
Application.Storage.deleteValue()
Application.Storage.clearValues()

Application.Properties.setValue()

I don't use any of these methods. The only thing I use is getProperty, like I wrote in the first post. Is it possible that during an activity another app is interfering and throwing this error? I know the user has Datarun premium and Datarun plus running as datafields when it crashes, but STORE_ID 6b9d2d26d7464377830e83422e3df45b in CIQ_LOG.TXT doesn't match the ID's in both datafields.....
I tried to look up with this ID from the log file, but https://apps.garmin.com/en-US/apps/6b9d2d26d7464377830e83422e3df45b does only return an error

Former Member over 8 years ago

If the ID does not correspond to your app, then it was probably not generated by your application. Does the modify time of the log correspond with your application crashing?

jim_m_58 over 8 years ago

This is where the new CIQ_LOG files in CIQ3 will be nice, as you get far more info in the file.
https://forums.garmin.com/forum/deve...ye-ciq_log-txt
It will be easier to see what apps caused it, when it happened, etc.

Former Member over 8 years ago

Hey. I checked and the the URL you had didn't contain the correct '-' marks in the store id. It ended up being this app: https://apps.garmin.com/en-US/apps/6...e-83422e3df45b

Forecast Line does use backgrounding and was updated a couple of days ago. It shouldn't be causing issues with your apps though. So you are getting a crash here, but it's not printing out to the CIQ_LOG then...If you want, you can send us early bird access at [EMAIL="[email protected]"][email protected][/EMAIL] and we could try and reproduce this for you. Just make sure to link this forum post so we can reference it.

Thanks,
- Coleman

jim_m_58 over 8 years ago

Coleman.. I think you meant "link" this post and not "like" this post, but since it was your 1000th, I did like it! :)

Former Member over 8 years ago

Please Like, Comment, and Subscribe

Former Member over 8 years ago

Well according to the forums I now have "a spectacular aura about" thanks to those likes. #worthit

-Coleman

GHG23 over 8 years ago

Thanks Coleman.ConnectIQ!, I tried a few '-' marks in the URL but it didn't work. The user is curious himself also now, so I expect that he can check whether Forecast line was the culprit.