A lot of people started FatWatch this morning and discovered that July 31 is missing from the FatWatch log. The good news is that this bug is fixed in FatWatch 1.1; the bad news is that FatWatch 1.1 is still sitting in Apple’s review queue. Nuts!
Not being able to enter your weight, which is pretty much the whole purpose of the app, is pretty terrible. If anybody has purchased the app and wants a refund, please contact me and we’ll figure something out.
The reason for this mess is because FatWatch only cares about dates, not dates-and-times, but the iPhone (and most computers) work with dates as timestamps. When you weigh-in on July 21, FatWatch only cares about the year, month, and day —- whether you weighed yourself at 7 a.m. or 4 p.m., it doesn’t care.
So, when it gets the date from the system (like fetching today’s date), FatWatch strips away the time. And when it needs to give a date to the system (to format it in your selected language), it adds the time back in. The problems are occurring because FatWatch 1.0 should take your time zone into account when adding and removing the time from a date, but it doesn’t. As a result, sometimes the date is off by a day, because the time added in pushes it into the next day.
FatWatch 1.1 fixes this by making sure to take your time zone into account. I wish there was a way to get it to you faster. If it makes you feel any better, I am living with this problem too —- I do my development on a test iPhone and keep my personal iPhone “clean”, meaning I won’t get to use FatWatch 1.1 for my own weight until everybody else does.
