TM 3.8 Crashes

[davidm]

I'm running Time Master 3.8 on an iPod Touch (2nd Gen) under iOS 3.1.3.  I was not having any problems with TM 3.7.   After upgrading to 3.8 it's started crashing back to the iPod menu when looking at a Time Entry and then hitting either Cancel or Save.  Anyone else seen these types of problems with 3.8?  Thanks.

[Adam]

Please try Rebooting your device.  A few people have written that they have had crashing with the 3.7 & 3.8 updates, but we have not received any crash reports from Apple.  We believe there is some sort of memory issue when upgrading.  So far, the reboot has worked for everyone who has done it.  Press and hold the power button on the top of the device.  Swipe on the "Swipe to power off" prompt and wait for it to shut down.  After it has completely shut down, press and hold the power button for a few seconds for the Apple Logo to appear.  Try Time Master next.  Please write us back if you continue to have any problems!

[davidm]

Tried that already.  I think I may also have some additional information about this as well.  It seems that if I edit a Time Entry that is so recent that I don't have to scroll down at all, I can edit it and save it without TM crashing.  However if I have to scroll at all (even one entry down) it will save the changes, but then crash back to the iPod menu.

[emptypage]

I have exactly the same issue. And editing the start time is something I do a lot. I have a 3g, iOS V 4.2.1, Time Master 3.8.

[Ernesto]

I couldn't reproduce this here yet. I'll make another run of tests tomorrow.

We had two other users report this problem, and rebooting it solved it for them, but we'll try to see if we can spot something.

Please bear with us while we investigate this.

Thanks,
Ernesto.

[Ernesto]

An update on this issue. I've finally been able to reproduce and identify what is the problem.

It's related to changes we did to the table header, so tapping on it wouldn't trigger a timer start accidentally.

It's a timing-related bug, which means it doesn't happen all the time, but it can happen and it's more frequent on slower devices.

Unfortunately, there's no workaround for it. I've fixed the issue on the beta version of our upcoming release, and we're hoping to be pushing that to Apple early next week. After passing the approval process, it should be in your hands.

We apologize for the inconvenience this has caused all of you, and thank you for reporting the issue.

Ernesto.