This has suddenly happened.
I had been developing a data field quite successfully and it now works well on my watch FR255.
I had to write conditional lines of debug code to spoof the objects workoutStep and workoutInterval step using Monkey C's duck typing to make development easier as the simulator doesn't bother to implement this, essentially writing my own conditional workout simulation.
Yesterday the device simulator stopped bothering to reliably update elapsed distance. It is not null. It might update once to a non-zero value.
Why do I have to do work that should have been implemented in the simulator.
Why should I have to debug your development environment in order to develop?
I am worried that you have one or more inexperienced developers who you are entrusting to do tasks that for you are low priority. They can do lots of damage that will be hard and take time to fix.
P.S.
You have fixed the embarrassing tiny font debacle on two value data screens. I would feel ashamed about this software being released out of beta.
What about fixing:
The failure of ALL CIQ fields to run (app error icon) on structured workouts when accessed via the race app. (no sandbox / memory?)
The failure of structured repeats to work when used with track mode. (skipping recovery, bonkers additional distance at a monotonic speed)
The failure of structured repeats to update after editing until the activity is exited and re-entered.
You have serious software quality control issues. Your watches aren't cheap. There really is no excuse.
P.S. dont reply to this if it is going to be a dumb and patronising one.