Forerunner 165 CIQ Apps crash since Firmware update 22.22

aceholgi 5 days ago

Hey,

starting today (19. Feb) FR165 customers report crashes of our apps as they installed the latest firmware 22.22. Lots of "Symbol not found" errors in ERA viewer, just with that device / firmware combo. Before, the apps were running without issues for months. Do you see similar problems?

Cheers.

Top Replies

Stanislav.Bures 2 days ago in reply to Kyle.ConnectIQ +2

Please fix this as soon as possible. Those of us who sell apps are now facing a lot of criticism and getting negative reviews. I have to answer a lot of emails every day and customers are not very understanding…
FlowState 2 days ago in reply to jim_m_58 +2

jim_m_58 said:
It's kind of interesting this didn't come up with the public beta FW as it could have been stopped or fixed before it was released. Are people not using public betas?

Are you using…
Kyle.ConnectIQ 3 days ago +1

We're looking into this and will be working on a fix. In the meantime, using has checks will prevent the crash. I can confirm this is only affecting the fr165 and fr165m.

All Replies

jim_m_58 5 days ago

How many do you see? You could be seeing the same user crashing multiple times if everything in the crash log is the same,

What specifically are you seeing in the crash log? Any clues there? Like maybe a setting that doesn't work right in all cases?

The FW on the 165, 265, 965 is actually pretty similar, and if you see nothing with the 265 or 965, look at the stack trace to see what's crashing on the 165.

aceholgi 5 days ago in reply to jim_m_58

If I sum up the different apps, it is a few hundred within some hours. 5 different languages up to now, all FR165 22.22, no other devices.

Garmin is rolling out a 22.22 on other Forerunners right now, let's see if these devices will be affected, too.

pstoppani 5 days ago

Yes, I'm getting the same crashes.

For me, it is a call to Dc.drawRadialText().

jim_m_58 4 days ago in reply to pstoppani

Just a guess but when you do the getVectorFont call, are you supplying optional fonts or just one? If just one, could be it's no longer available.

Be sure what you get back from getVectorFont isn't null, because if is. calls like dc.drawRadialText will crash.

Shent-Aurkhan (SHN) 4 days ago in reply to pstoppani

hi, I also have this crash, I use:

var vf = dc.getVectorFont({:face=>["BionicBold","RobotoCondensedBold","SakkalMajallaBold","Swiss721Bold","NanumGothicBold"], :size=>sz});

but according the device reference guide, the 2 first are supposed to be on the FR165, I think it is a device issue.

aceholgi 4 days ago

Thanks for all your replies! Let's hope that Garmin doesn't intentionally downgrade the FR165 to Vivoactive 5 level (no vector fonts, no alpha channel for drawing primitives)

jim_m_58 4 days ago in reply to Shent-Aurkhan (SHN)

I have a WF that will use scalable fonts if available including the null check for what's returned by getVecorFont. It uses a standard font and drawDraw if there is an issue (for the date at the top). Feel free to grab it and make make changes to the fonts attempted if you want to use something simple to reproduce this in a bug report.

https://forums.garmin.com/developer/connect-iq/f/discussion/349473/simple-example-wf-that-shows-a-bunch-of-things

Shent-Aurkhan (SHN) 4 days ago in reply to jim_m_58

Many thanks! It is what I do, the issue is not here, the issue is since the 22.22, some FR165 remove the scalable font which were available before this update and worked perfectly.

jim_m_58 4 days ago in reply to Shent-Aurkhan (SHN)

Or it could be something is wrong with getVectorFont on that device/FW level. Maybe they simplify removed the ability to use scalable fonts all together for some reason.

I'm using 22.22 on a 965 and the vector fonts work fine.there so maybe something else to note in a bug report. I don't have a 165 to try things on but maybe someone that does can assist.

FlowState 4 days ago