SDk 4.0.1 and ConnectIQ settings crash app

Hi,

New problem on latest release of my app using latest SDK. Sending settings to app works fine if app is running. If the app is not running then on the next restart it crashes almost immediately. Only solution is reinstall and lose all data (if only we could save app data...).

Simulator works fine.

The code has not changed in this part of the app for a long time and has always worked before.

Suggestions much appreciated

Regards,

David

davidmct-g over 4 years ago in reply to davidmct-g

Sadly I was wrong. 44 crashes with unhandled exception on the first read of a property in onStart(). I can't debug this as it works fine on the simulator and my debug log stops just before the first property read on the actual watch. Try/catch has no effect as it's "unHandled". I suspect corruption of the Properties store when CONNECTIQ writes new values when the app is not running. Works fine if app is active as change is handled in the code.

We could really do with the ability to check the contents of storage/properties on the device for our apps from our debug environment. ideally copy data from watch and then see structure!!! Even just being able to read the properties as an array/dictionary of data which we can write to a log would be something if it use the memory system directly.

I have run out of ideas on how to find this.

davidmct-g over 4 years ago in reply to davidmct-g

I made the following changes which have for some unknown reason solved the issue for now.

1. First property read in onStart() changed to storage. Property load moved to end of onStart()

2. Deleted all properties that are not also settings and changed them to storage where possible

I feel that there is some sort of limit on the number / size of space taken by properties depending on the watch as previously I had random crashes (unhandled exceptions) on the read of a list of properties at different ones depending how many there were. It also seemed to apply to FIT data structures as well.