Acknowledged

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.

Parents
  • They both use the result of getVectorFont.  So "has" check that, and if has shows true, also check that what you get back isn't null, and if it is, don't use drawRadialText or drawAngledText.  That's what I've done since scaled/vector fonts were introduced.

    You may also want to add "has" checks for drawAngledText and drawRadialText for extra protection

Comment
  • They both use the result of getVectorFont.  So "has" check that, and if has shows true, also check that what you get back isn't null, and if it is, don't use drawRadialText or drawAngledText.  That's what I've done since scaled/vector fonts were introduced.

    You may also want to add "has" checks for drawAngledText and drawRadialText for extra protection

Children
  • 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

  • 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?

  • Then remove the 165/165m from your supported devices until this is fixed.  I've done that in the past for other issues on other devices.  In one case the fix took over a month.

  • 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. They'll come back to the developer, not to Garmin on this. It's the dev who needs to reply to dozens of emails and explain the issue. Some people want a refund...