Problem with an app for FR235 that was ok before !?

Hello !

I made an app watch some months ago for FR235 (or watch with HR included) and after more than 3500 download, users were very happy. But 2/3 weeks ago, i start to receive messages from users who can't use the app watch after download (they download and nothing appear in IQ app on the watch).

So after 6 messages, i just reload and rebuild the code with the last SDK (1.2.9), i thought "maybe there's a bug with last firmware on FR235 and not the last SDK used when i published it ?". I also check if on the simulator, the app was still OK.

But it seems that even with a rebuild SDK 1.2.9, there's always the same problem...

So, do you know what happen or if a function changed ??

Thanks a lot !!

jim_m_58 over 8 years ago

I did find something with HR on the 2.62 beta firmware on the va-hr, and this may be the same on the 235 if the users are running the beta FW on that. When checking for a valid sample from the History, it used to be that you saw "INVALID_HR_SAMPLE", but with at least the va-vr, instead you'll see a null. So in the following check, I had to add the underlined:

if(hrs!=null && hrs.heartRate!=null && hrs.heartRate!=ActMon.INVALID_HR_SAMPLE) {

Still building on 1.2.x, but works with the beta FW. It's a bug in the beta FW and has been reported. Nothing wrong with the SDK.

Domioffroad over 8 years ago

Thanks a lot for your response.
I will add the 2nd condition in the test, but i'm pretty sure that users with problems don't use a beta firmware version. I will ask them to verify.

Best regards

VivoactiveHRGuy over 8 years ago

I did find something with HR on the 2.62 beta firmware on the va-hr, and this may be the same on the 235 if the users are running the beta FW on that. When checking for a valid sample from the History, it used to be that you saw "INVALID_HR_SAMPLE", but with at least the va-vr, instead you'll see a null. So in the following check, I had to add the underlined:

if(hrs!=null && hrs.heartRate!=null && hrs.heartRate!=ActMon.INVALID_HR_SAMPLE) {

Still building on 1.2.x, but works with the beta FW. It's a bug in the beta FW and has been reported. Nothing wrong with the SDK.

Thank you .. it is appreciated.

Domioffroad over 8 years ago

OK the users with the problems don't use a beta firmware... :-(

Does somebody with a FR235 can just download the app and say what's happen in fact ? (difficult to have real description from users...)

Thanks a lot

HermoT over 8 years ago

OK the users with the problems don't use a beta firmware... :-(

Does somebody with a FR235 can just download the app and say what's happen in fact ? (difficult to have real description from users...)

Thanks a lot

Do your users perhaps have 4.70?

There is a known issue with 235 and FW v 4.70.
The issue is specific to time not being shown correctly, and I am suspecting that the issue is with Lang.format(). So if you use that, it could be what is not working on the 235 for these users, provided that they have 4.70 FW installed.

Please see this thread

Domioffroad over 8 years ago

Oh yes !! it's look like this problem ! They have 4.7 firmware installed...

Thank you very much

HermoT over 8 years ago

Oh yes !! it's look like this problem ! They have 4.7 firmware installed...

Thank you very much

Unfortunately there is nothing much we can do other than waiting for new FW with fix.
Or perhaps you could use + operator to build up your string instead of using the Lang.format()?

I detest having to make these kind of fixes (hacks) because of some bad FW.
I have decided to not "fix" (and I really mean "hack", cause the code is correct in the first place) mine and rather point the users to the relevant thread so that they can see that the fault is with Garmin and has nothing to do with the quality of your code.

Domioffroad over 8 years ago

I agree with you... I prefer to inform users and keep my code (and my fingers crossed :-)) until a new FW is deployed !