SensorHistory with :period attribute crashes in simulator, not on real device.

km19 over 4 years ago

This 2 lines:

var dur = new Time.Duration (60*60);

var iter = Toybox.SensorHistory.getPressureHistory({:period => dur});

crashes running watch face in simulator, but on real device it's working ok.

Error: Unhandled Exception

Exception: UnexpectedTypeException: Expected an object of type Time.Duration

Can you Garmin do something about that ?

Simulator version: 3.2.4

4 years ago there was similar issue: forums.garmin.com/.../simulator-crashes-when-using-period-in-options-of-sensorhistory-getxxhistory-methods

Travis.ConnectIQ over 4 years ago

This issue was recently filed as WERETECH-10767 for this post. The issue has been triaged, but has not been fixed.

You should be able to work around the problem by catching the UnexpectedTypeException in you app code.

km19 over 4 years ago in reply to Travis.ConnectIQ

Thank you for your replay. I have related issue with SensorHistoryIterator.getMax() function:
- documentation describes that is should return a Number:
getMax() ⇒ Toybox.Lang.Number

while an example shows an SensorSample object:

System.println(sensorIter.getMin().data);

Non of this seems to work on device (fenix5s).

jim_m_58 over 4 years ago in reply to km19

getMax() returns a Number, so you don't want to use sensorIter.getMin().data, just sensorIter.getMin()

Looks like there is a mistake in the sample code.

km19 over 4 years ago in reply to jim_m_58

I tested it on device and in my case (fenix5s, getPressureHistory with :period attribute) getMax () function returns something which is not null nor Number. It doesn't pass this statements:

var max = iter.getMax();

if (max instanceof Number) {...}

if (max == null) {...}

if (max has :data) {...}

I am sure that Iterator is not null - I got a proper value via iter.next() function, so getMax should return a proper value.

jim_m_58 over 4 years ago in reply to km19

In what you posted you had:

sensorIter.getMin().data

That's what I mean.

km19 over 4 years ago in reply to jim_m_58

Why? I don't. I have iter.getMax () and I am testing it against above validations. The last one is just a double check.

km19 over 4 years ago in reply to km19

in case of getPressureHistory it's Float not Number.
So there is double bug in the documentation as well:
- wrong sample code

- getMax, getMin function can return Number or Float

Travis.ConnectIQ over 4 years ago in reply to km19

Please post a bug report in the Bug Reports area. I've stopped moving posts from Discussion because they tend to lose replies.