Archived:Wireless Messaging API with Push registry behaves inconsistently when receiving several SMSs in S60 (Known Issue)

Comments

This comment regards the Solution: "Signing the MIDlet solves the problem and allows the MIDlet to launch automatically. "

Which level of signature solves the problem?

3rd party should do it?

Thank you for your feedback. The solution of the article has been updated - signing the MIDlet with the Identified Third Party Protection Domain certificate solves the problem.

Forum Nokia KB 13:34, 13 November 2007 (EET)

Well... its not helping.... My application is signed by java verified.

---

After signing, you need to change the Autostart application security setting to "always allowed".

Forum Nokia KB 15:17, 6 February 2008 (EET)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Tested with

Devices(s): All S60 2nd and 3rd Edition devices

---

Compatibility

Platform(s): S60 2nd Edition, S60 3rd Edition, S60 3rd Edition, FP1

---

Article

Created: User:Technical writer 1 (October 19, 2007, updated February 6, 2008)

Last edited: hamishwillee (28 Jun 2012)

Overview

When sending several SMSs between two S60 devices, WMA with PushRegistry behaves inconsistently in the receiver device.

Description

When sending several SMS messages (5-10 or more), the unsigned receiver WMA MIDlet using PushRegistry will perform inconsistently when launching it, for example, resulting in slow queuing of received SMSs or SymbianOSError messages. Sometimes, especially when receiving 10 or more SMSs, launching fails and the receiver application crashes without error messages or exceptions.

How to reproduce

Download the WMAExample MIDlet and install the unsigned application on two S60 devices. By using the other device’s MIDlet, send 5 to 10 SMSs to the other device. After sending all the SMSs, launch the MIDlet on the receiver phone.

Solution

Signing the MIDlet with the Identified Third Party Protection Domain certificate solves the problem and allows the MIDlet to launch automatically. After signing, you need to change the Autostart application security setting to "always allowed".