Acknowledged
4 months ago

22.22 FR165 DrawRadialText symbol not found

Since the last update, 22.22, method Dc.drawRadialText stopped working on the FR165 and FR165m.
It works fine in the sim, but crashes on a real device with error "Symbol not found".

I reported this last month when it was still in Beta as well: 

https://forums.garmin.com/beta-program/forerunner-165-series/forerunner-165-series---bug-reports/i/public-beta-version-22-xx/drawradialtext-symbol-not-found-in-dc

Now the software is rolling out, apps that use this will method will crash (including two of my watchfaces) with no easy way to work around this.

GreenBlack
  • 4 months ago

    > And can they still change the settings through the IQ app? Or would this be blocked since they don't have the latest update?

    I think you should be able to change settings for older versions of apps. (Afaik, the app settings metadata stored on the backend should be available for previous versions, not just the current version, same with the developer FIT field-related metadata).

    > Removing devices from the manifest is not the way to go, as it won't prevent existing customers from sending emails

    I agree that removing devices *alone* is not the ideal solution.

    > Jim, it won't make the customer happy to have a completely messed up watch face (they paid for) due to wrong layout / font size text angle etc. instead of a crash

    If it's not possible to change the app so it works without the affected functions that you need (getVectorFont, drawRadialText, etc.), I guess a compromise could be to display a message to the user explaining that's there's currently a bug with their device which prevents your watchface from working properly.

    So you could do both things:

    - remove affected devices from the manifest

    - add an in-app message to users on affected devices explaining the problem

  • 4 months ago in reply to Roboleo-Apps

    They could have it figured out today, but if it requires a change to the FW (I'm guessing it does) the fr165 group  determines when that happens.  And in general, CIQ issues aren't a real high priority for the platform groups 

    There was one case where a bug I reported on the va5 that was easy to reproduce didn't get the needed FW fix for months.

  • 4 months ago

    Removing devices from the manifest is not the way to go, as it won't prevent existing customers from sending emails. A good way is to ask people to upvote this bug report to "help" prioritize it. As Kyle already wrote, they are working on a fix. I'm trusting in him to get it done hopefully sooner than later. 

  • 4 months ago in reply to GreenBlack

    Chances are they will change to something else if the one they are using keeps crashing, but new folks won't be able to try it and get frustrated/angry.

    And for paid apps ask for a refund, even though the dev isn't responsible, because they paid for something that doesn't work.  They don't care who's responsible.

    My apps that can use scalable fonts were written in a way that they also work on devices without scalable fonts but with a different look and don't crash

  • 4 months ago in reply to jim_m_58

    What happens to the users who have installed/bought this already, when removing their device from the manifest? Do they simply not get the update, or would it remove it from the store for them? Maybe even completely remove the app from their watch? And can they still change the settings through the IQ app? Or would this be blocked since they don't have the latest update?