Multiplication of doubles from properties fails on watch only

I have 2 properties:

-------

var cst= 0.00;

var amt = App.Properties.getValue("StockCount_0") ;
var price = App.Properties.getValue("StockPrice_0");

cst = amt * price;

Runs fine in emulator.

When I run on the watch I get an IQ! screen crash and it looks like it happens during the multiplication operation.

jim_m_58 over 5 years ago

See https://forums.garmin.com/developer/connect-iq/w/wiki/4/new-developer-faq#settings-crash

You may need to do something similar.

rwgreen1173 over 5 years ago in reply to jim_m_58

Not sure I am following? This is not a issue with null values.

I am trying to multiply two doubles and I think the watch crashes?

jim_m_58 over 5 years ago in reply to rwgreen1173

It could be that what you are seeing is a string vs a double, so in readKeyInt it makes sure the value is a Number and not a string. Try the same type of logic.

You could be getting the crash as you are trying to do math on a string.

rwgreen1173 over 5 years ago in reply to jim_m_58

Not sure where or what is a readKeyInt or where to see it.

I am setting the property (defined as a double) to 15 and 7.62 respectively.

jim_m_58 over 5 years ago in reply to rwgreen1173

readKeyInt is in the section of the New Developer FAQ I linked to

https://forums.garmin.com/developer/connect-iq/w/wiki/4/new-developer-faq#settings-crash

It's a wrapper function to insure when a property is read, it's a valid type.

rwgreen1173 over 5 years ago in reply to jim_m_58

Are you saying that the properties definition of type = "double" does not ensure that getValue is a double and could be a string? I mean I am literally setting the property myself.

jim_m_58 over 5 years ago in reply to rwgreen1173

Yes, that has been the case of Numbers.

That's why there's that section in the New Developer FAQ.

flowstate over 5 years ago in reply to rwgreen1173

If the property is tied to an app setting, yes (unfortunately). There has even been a case when a numerical property can be returned as null, if the user enters an invalid value for the associated setting.

forums.garmin.com/.../gc-mobile-ios-setting-returned-as-null-if-non-numeric-entered-for-numeric

jim_m_58 over 5 years ago in reply to flowstate

readKeyInt handles that in addition to the value being the wrong type.

flowstate over 5 years ago in reply to jim_m_58

I understand that. I'm just explaining the kinds of bugs / unexpected behavior that's been seen in the past, for context.