Gemalto is now part of the Thales Group, find out more.

You are here

destroyApp() not called by at^sjam=2 | Thales IoT Developer Community

September 26, 2016 - 9:12am, 2696 views

In our application we're using 3 instances of an ATCommand, which appears to be the maximum amount. Our application is an end-user device, in which it is not allowed for an end-user to turn the device off or reboot it (this is under software control).

When we autonomously update the application, we need to stop the midlet, install the new one and start it.

It now appears that the at^sjam=2 command doesn't call the destroyApp() method, causing the ATCommand instances not to be released and hence starting the new midlet fails because the ATCommand instances are exhausted.

Why is the destroyApp not called, this seems very logical to release resources, there is currently no other way in doing this or is there another method to release the resources?