• Replies 35 replies
  • Subscribers 28 subscribers
  • Views 2761 views
  • Users 0 members are here
Options
Related

Forerunner 165 CIQ Apps crash since Firmware update 22.22

aceholgi
1 month 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.

  • 13 days ago in reply to Roboleo-Apps

    So the issue isn't solved after 2 months. With SDK 8.x, support of drawRadialText() and drawAngledText() was dropped on the FR165. Therefore we have currently two choices: Discontinue support of FR165 on existing apps when compiling with SDK 8.x. Or stay with SDK 7.x for existing apps to further support customers who paid in the past for the app - but then the app won't be available to new devices like the Vivoactive 6, which isn't available under SDK 7.x. That's a BAD situation and totally avoidable by Garmin.

  • 12 days ago in reply to aceholgi

    The issue was fixed by Garmin an hour ago. FR165 is compatible with SDK 8.x by now.

  • 12 days ago in reply to aceholgi
    aceholgi said:
    FR165 is compatible with SDK 8.x by now.

    It doesn't matter anymore for this problem, but I have to reiterate:

    - the issue was in the device files, not the sdk

    - you can't use an older SDK in any case, since 8.1.0 is required to build for fr165 (and many other devices) now

    - even if you could use an older SDK, it wouldn't have fixed the problem (the issue was in the device files, not the sdk)

  • 12 days ago in reply to FlowState

    Yes, I just got updates to the fr165 and fr165m device files and looking at the differences, the main thing is the addition of symbol="drawRadialText" and symbol="drawAngledText" which were missing in the previous versions.

    That is independent of the SDK itself.

  • 11 days ago in reply to gasteropod
    gasteropod said:
    That is independent of the SDK itself.

    Exactly.

    Couple of things that probably lead people to believe this problem (and device configs in general) is tied to the SDK version:

    - both changes (removing and adding the functions in question) were in the SDK changelogs. (The changelog for 8.1.1 actually implied that the functions were added back, and the 8.1.1 local API docs reflect that fr165/fr165s support those functions, although 8.1.1 was released before this actually happened)

    - both changes are reflected in the corresponding local SDK API docs (in the Supported Devices section for the functions)

    This kind of thing can probably be explained by:

    - device configs actually used to be distributed with SDK versions. (Apparently Garmin started releasing device configs independently of SDK versions because they didn't want to release a new SDK "point version" every time a device config was updated, but we did lose the ability to roll back device configs by simply changing the SDK)

    - the API docs were probably designed with that in mind

    - even when the device configs were decoupled from the SDK versions, the API docs still have to say which devices a function supports

    The way it *used* to work (device configs tied to SDK versions) is the way lots of people seem to assume it actually works, and it's hard to blame em. Just judging from the local SDK API docs, you could easily get that impression. e.g. if the local docs for SDK 7.4.3 say that fr165 supports drawAngledText and the local docs for SDK 8.0.0 say that fr165 does *not* support drawAngledText, then it wouldn't be unreasonable to assume that rolling back to SDK 7.4.3 would restore support for drawAngledText, but this is not the case.