[UPDATE]: On 9/30, Apple sent an email to us acknowledging that this is a known bug in their developer tools/code, and the say that it "is currently being investigated by engineering."

We have now had two users report a bug where the Stop Timer scrolls back to the start time when they attempt to stop a timer and the start and stop times straddle noon.

After quite a bit of research, we have finally been able to replicate those user's reports.

It's actually a bug in the iPhone/iPod OS, and we've reported it to Apple. We hadn't seen it in our earlier tests because it didn't exist in earlier versions of the OS.

The problem is that, when a user has his/her date and time format set to 12 hour (as most people from the USA would), when the time is scrolled forward to noon, the AM/PM specifier gets scrolled forward to "PM" as you would expect, but the backend code in Apple's development tools still think that it's AM - thus, it believes that you have scrolled to midnight (or 1 AM, or 2 AM...).

Note that this ONLY happens when:
1. Your time format is set to 12 hour, and
2. The time picker defaults to a time before noon, and you want to scroll it forward to a time past noon. Since TimeLogger defaults to the current time, if you are stopping a timer when you stop a task, this should not affect you.

If your time format is set to 24 hour or you don't stop timers except at the time you stop performing a task, this won't affect you.

There are 3 potential solutions:
1. The easiest - The bug seems to be evident when ONLY the hour column is scrolled in the picker. If you scroll the minute selector forward or backward prior to moving the hour picker, you ought to be able to get past the symptoms.
2. More difficult, but still works - When you need to straddle noon (or when you have this issue), move the AM/PM specifier to PM first, and then roll the hour specifier BACKWARD to the desired hour. If you roll it forward, it will switch back to AM when you hit 12.
3. Probably not the most desirable solution for those in the USA - Set your date and time format to 24 hour.

Regardless of the fact that it isn't our bug, we will be working to implement a work-around so that it won't affect our users if we feel that it is taking Apple a long time to address the problem.