Posted on

Version 1.3.17 released

An IQ! error appeared on Dec 6 for users using stock information. This is due to the stock information supplier being in maintenance and the code not handling this event properly.

The code has been updated on the server and in the watchface code to handle any unexpected stock data without causing an IQ! error.

Posted on

Version 1.3.16 released

Following feedback of several users with various devices, and especially Fenix 6 Pro Solar users, there has been several updates pushed in a short period of time, to remove bugs and add features.

  • Added datapoint 11 (weeknumber)
  • Added datapoint 93 (battery charge)
  • Reinstated datapoint 54.1 and 54.2 (that were removed temporarily for memory reasons).
  • Fixed bug related to stock price.
  • Fixed out-of-memory error that occurred on Fenix 6 Pro Solar (and any 280px screen watch).
  • Wind direction now NNE style (3 characters) in addition to NE (2 characters) and N (1 character).
  • Internal temperature can be selected as datapoint 34.
  • Distance fixed (now in km or miles as expected).

Future updates will come at a slower pace, and will be released in the Beta channel first to ensure stability.

It is increasingly difficult (if not impossible) to add more features because the memory limit of the program is reached and memory optimization has been carried out.

Posted on

Stock service disruption

There has been a disruption on stock service from Nov 28 to 30, due to an upgrade in the stock service account with our supplier, but a glitch in the activation of this upgrade.

Service has been resumed on Dec 1 at 5am GMT and there is no further disruption planned.

Posted on

WorldFace Beta channel

I created a beta channel for WorldFace to improve the user experience.

I noticed that when publishing updates (mostly to add features following user requests), there are often bugs that require new updates. Sometimes, those bugs are linked to the settings and the Garmin system, which I am not fully in controlled of. There seems to be a limit not only to the size of the app in Kb, but also to the number/size of settings. And those limitations seem to vary with the device model.

Since I only own one model, a D2 Charlie, I can only test on my watch. I normally release updates only when I am satisfied with testing. But I noticed users reporting issues on other devices (like the Fenix 6) that I have not experienced on my device.

As a result, I will now post updates on the beta channel first. Hopefully, some users will be using the beta app to test and report if any bug is encountered.