Did something change with Framework 3.1 that affects stats?

[jomis003]

I am getting emails from people using my watch faces and are reporting that since the beginning of April stats have started showing NaN instead of the number and the HR has stopped reading. 

I have been able to get most of them moving again with a watch reboot or a uninstall/re-install but not all of them. 

Did something significant change in 3.1 with the way stats are collected and displayed? Is anyone else hearing the same thing from their customers?

[JonFitbit]

Can you ask them to switch to a different clock, and switch back again?

[jomis003]

@JonFitbit  - I have been able to fix most of them by either rebooting The watch or having them install a different watch face and then coming back to it, however I do have some where it seems as if the heart rate sensor is not even firing.

I even have one where the heart rate is registering 40 to 50 beats higher  but it should be and what it is with other clock faces.

[jomis003]

 @JonFitbit  here is an example from one user that just reached out to me just now. Notice how there is no stat any longer next to the heart rate and the distance is a NaN.

[EmTe]

I've had similar feedback too for my watch faces.

[jomis003]

@JonFitbit  -  I am still getting support requests for people all of a sudden getting no stats and NaN. Is this happening when the OS is being upgraded to 3.1?

I have been having them reboot first, then install a new face, reboot and reinstall my face. As a nuclear option I have been having to tell them to factory reset their device. I have had mixed results and the only consistent thing is unhappy customers. 

Has there been a root cause determined as to why this might be happening? If it is a change in coding, I am happy to re-mediate, but at this point the only thing that has changed is the OS version.....