Hi,
I have a weird one where, because I don't have access to the phone / watch in question I cannot verify whether this is an actual bug or instead a customer-specific phone connection issue. So... putting this out there in case somebody has encountered similar.
This is the situation:
1. I have a WF with numeric settings used to store float values
2. Somebody using the WF in a locale with comma rather than period as decimal settings is having problems setting these values using Garmin Connect IQ app on iPhone
3. At the moment, it looks as if the numeric values are either not recognised at all or wrongly parsed - they are set but have no effect
4. When adjusting these values in Garmin Connect IQ app on his iPhone, the numeric separator is dynamically replaced to comma rather than period. EG: He claims to paste "63.125" and it is entered as "63,125".
5. However, I am aware that Garmin parses strings to numeric data using period as a separator.
5. As I don't have access to the watch / phone in question, I cannot verify any of this...
It is entirely possible that the Connect IQ behaviour is actually both deliberate and kinda cool - eg: it could be automatically interpreting locale-specific separators and storing a purely numeric value in properties and that the customer's problems actually lie somewhere else in the chain. (I suspect his phone/watch network connection, for example.)
It is also entirely possible that the string with locale separator is stored as the underlying data and then fails to parse correctly when read by the watch later.
Has anybody else found this?
Any suggestions to debug further?
G