Complete
over 4 years ago

WERETECH-10767

Fixed

CIQ 3.2.5/3.2.4 sim getHeartRateHistory error with :period option

using  small values calling

getHeartRateHistory

with :period option with short duration (28, 3)  cause error

Error: Unexpected Type Error
Details: Failed invoking <symbol>
Exception: UnexpectedTypeException: Expected an object of type Time.Duration

You need close sim and start again to run propper

_psx_
Parents
  • over 4 years ago in reply to Travis.ConnectIQ

    I have such situation everyday, not form time to time, everyday. There is a lot of errors, are there any automatic tests for all api? There is no big api so could be tested simple everything... But now developers are ... testers. I don't  think I'm alone who has errors.

    But the most frustrating thing is not fixing errors by Garmin. Why? Why known error aren't fixed?

    If something wrong happen in car everybody go to mechanic to repair it. Is any button or gear in car which is assembled by producer and it always not run well? No  if such  happen is repaired or removed...

    Simple example  if(x)  for x=null rull run well but for if(x && true) no, exception...
    its' known for ages. I'm sure in 100% that every new  developer  meets this problem, even old one forget and ... exception and thinking what's going on????aaaa.... Garmin doesn't want to fix it, and ==null and (has :...) an more code, less memory, and time and nerves...

    Instead of fix errors Garmin produce ciq 4, which is not compatible in 100% with previous ciq for everybody who use buffbmp's, so there will
    - old errors
    - new errors
    - incompatibility errors
    - and of course developer's error
    so, it's not strange that simple application is written in months  or years

Comment
  • over 4 years ago in reply to Travis.ConnectIQ

    I have such situation everyday, not form time to time, everyday. There is a lot of errors, are there any automatic tests for all api? There is no big api so could be tested simple everything... But now developers are ... testers. I don't  think I'm alone who has errors.

    But the most frustrating thing is not fixing errors by Garmin. Why? Why known error aren't fixed?

    If something wrong happen in car everybody go to mechanic to repair it. Is any button or gear in car which is assembled by producer and it always not run well? No  if such  happen is repaired or removed...

    Simple example  if(x)  for x=null rull run well but for if(x && true) no, exception...
    its' known for ages. I'm sure in 100% that every new  developer  meets this problem, even old one forget and ... exception and thinking what's going on????aaaa.... Garmin doesn't want to fix it, and ==null and (has :...) an more code, less memory, and time and nerves...

    Instead of fix errors Garmin produce ciq 4, which is not compatible in 100% with previous ciq for everybody who use buffbmp's, so there will
    - old errors
    - new errors
    - incompatibility errors
    - and of course developer's error
    so, it's not strange that simple application is written in months  or years

Children
No Data