Ok... I spent the entire weekend working on this, and I’m going to probably take a few days off to work on it full time this week.

Memory usage, unfortunately, is a bit of a problem again. But this time it appears it’s something to do with the iPhone OS and not the application. What clued me in was direct probing of memory hardware. It seems the OS, depending on the program lauches may or may not report back enough memory being available and either kills the application or shuts it down sometime during the programs execution. Simply starting it back up in a few seconds, and the program is OK.

Similarly, people have noted that sometimes they go to launch the program and it shuts down, even though it ran fine before. Restarting the device clears out the problem. Again, this sounds like a problem in the OS, though I can’t really prove it.

Another issue regarding version 1.0... people are reporting that they are getting warnings when small amounts of time have elapsed or that the food or water icon disappears before filling up to the top. This is a bug in the program and will be fixed in the next version. In the meantime just try not to get 3 full resets (otherwise you lose your iGotchi and the accrued time). Warnings and Resets will be set back to ZERO in the next update for all users, since this was my goof and not something most people did on their own. My apologies of course.

Why not fix it immediately.... again, this has to do with the development process and the application review process. If I put out a version to fix a minor thing, the app gets in the queue... if I update that again shortly thereafter, the app gets pushed back again to back of the line. I’d rather spend time improving as much as possible in the program than fighting the submission process.

Anyway... the next release is looking better from a code point of view. I’m hoping to get this out “soon”.