Acknowledged
4 days 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
Parents
  • 3 days 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

Comment
  • 3 days 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

Children
No Data