Friday 17 September 2010

Bug: Pause Causes Force Close

I've just seen a crash report in my developers console on the Android market. It looks like there is a bug in the pause functionality. I'm not sure exactly what causes this at the minute.

I will look into this over the weekend and will push out a fix as soon as possible.

Grrr. I hate bugs.

Update 1: Ok, having looked at the code I can see that there is a fairly fundamental flaw in the way the pause functionality is implemented. It's going to take a fairly major re-write to make this work correctly. Until then I'm going to disable the 'Pause' functionality. Which is not ideal, but better than having the app crash unexpectedly.

4 comments:

  1. Slightly off topic question.
    How do i transfer my sittings logs/profiles from one phone to another?

    Satpal

    ReplyDelete
  2. From the main timer screen:

    1) Menu --> View Sitting Log
    2) Menu --> Export Sittings

    That will create a file called exported-sittings.txt at the top level of your SD card. Copy the file to the top level of the SD card on your other phone then:

    1) Menu --> View Sitting Log
    2) Menu --> Import Sittings

    ReplyDelete
  3. Thanks for the quick reply.
    It didn't work at first, kept crashing.
    Then I realised that, because my new phone is a samsung galaxy, old one was desire, the top level directory of the sd card might not be the same.
    It was as I expected. On the Galaxy when you goto the file manager the top level directory is the internal 8/16gb partition and there is a folder under there that is called sd, which is the external sd card. The structure is:
    \sdcard <- samsung internal memory
    \sdcard\sd <- external added micro sd card this is where the exported sittings log was
    I did a copy & paste from \sdcard\sd\ to \sdcard and then tried to import the sittings log and hey presto it worked.

    Anyway it's all good now thanks again.

    ReplyDelete
  4. Thanks for the info. I'm going to make this functionality a bit more friendly so that it doesn't crash, and reports useful information (like where it expects the file to be).

    ReplyDelete

Note: only a member of this blog may post a comment.