[gblank]

I've been having this problem that on my 6230i when running mudlet and pressing red EndKey, the destroyApp is not called.
I can't seem to find anything regarding that issue.
Please advise.
Thanks.

[ericfu_88]

I am seeing this on the 6263 as well.

[hartti]

Do you mean the MIDlet does not exit or the MIDlet exits but the destroyApp is not called?

Hartti

[paulandrewgreen]

Hi all,

Don't know if this helps or is even relevant, but I experienced this issue and fruitlessly searched the discussion boards. I found my own answer and in doing so wanted to share the result so people don't make the same mistake that I did.

In my midlet, the destroyApp method was not being called when I pressed the RED key (hangup key) because my code WAS STILL IN THE "startApp" METHOD!

It kinda makes sense, because if you've not finished initialising there's probably nothing worth clearing up. However, if you open some critical files and (for example) start some form of data transaction, then these won't be cleaned because destroyApp is not called.

All that should probably be done in startApp is create a new instance of your main class (extending Thread of course) and call the run() method. (I am happy to be corrected on this). I suspect startApp was intended to return as fast as possible.

The moral of this tale is, even when creating test harnesses - DONT PUT ALL OF YOUR CODE IN startApp!!!!

I hope this helps, it certainly fixed my problem.

Oh and happy new year to all.

P