I've had my clock faces out there for months that have been reviewed by Fitbit and working fine.
Today, I got a support request describing this exact same issue. I had the person uninstall the clock face, reboot both the Fitbit device and phone, then re-install the clock face. At that point, everything worked and the customer was happy.
I later installed one of my older clock faces from the gallery as a test and had the same issue -- time and date worked, but the stats were not working. When I checked the permissions, the Activity toggle had been disabled and I made no changes to my clock. And I certainly did not change the toggle when I installed it.
I suspect that Fitbit pushed something out that affected some of the devices, or experienced some sort of outage or spike. I know that Fitbit got slammed over the weekend on several security web sites because of API vulnerabilities (related to the GAM -- I'm not making this up or trying to make trouble here). To Fitbit's credit, they were open and quick to reply to the folks who found it.
I don't understand why Fitbit doesn't use this forum to alert developers of upcoming changes or outages? That would make supporting my watch faces a lot easier. Instead, Fitbit seems to only use this forum to cheer-on new releases that are dropped without warning -- and seemingly without enough testing. Most of the developer questions posed are answered by other developers. And it seems that Fitbit has made it really difficult to development for legacy Ionic, Versa, Versa 2 and Versa Lite models without warning.
Speaking as a developer, this all feels like a bad implementation of Agile methodologies.
