EXTREME crashing!

Hi,
I've only started having extreme haypi crashes recently, I have no idea why.
The app has made my ipod HARD reset 3 times, when i went to:
letters
alliance chat, trying to send something
and when i opened the map

All of my other apps work perfectly fine, haypi is now generally crashing every minute I play forcing it self shut, sometimes i can't even open then app, let alone pass the UI without the game crashing

This used to be rare, as stated above, this has only started to occur recently.
I have un-installed and re-installed the app
I have turned my ipod on and off

update: after an hour or two, the crashing has smoothened down, it's not occuring so often now. I left my ipod off for around 2 hours.

My ipod is 2nd generation non-jailbroken 4.0.1

thats intense. my ipod started crashing when i play haypi, but its been more than 1 app that its been doing that. nothing about hard resets though thats intense.

It crashes a lot, after closing chat. I noticed this only after the recent update.

Yes this game crashes for me probably once every other week.

Mine has only crashed before the update

It crashes a lot, after closing chat. I noticed this only after the recent update.

i agree, but its more frequent now

Since installing the 2.02 update, I have experience MANY crashes. At several times, Haypi has crashed a dozen times over the course of a 10 minutes while in alliance chat. Sometimes I am just taken back to the dashboard. Other times, I get a hard reset as mentioned above. Could you put 2.01 back up so I can reinstall that version since it didn't crash nearly as often?

I am using iPhone 4 with iOS 4.0.

My game crashes at least 6 times a day since the haypi update.

this happened after the new update. I crash at least 10~15 times a day, and disconnect much more frequently. I know it's not a problem with my wifi or ipod. I'm sure Haypi is working on fixing this? I hope so. You just have to be more patient, and not click on things to hastely.

[Thomas]

Yes, it's a new bug of ver 2.02, has been fixed in ver 2.03, which has been posted for reviewing.