Archived:Custom-created message left in Outbox (Known Issue)

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}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

Created: User:Technical writer 1 (22 Dec 2005)

Last edited: hamishwillee (19 Jun 2012)

Overview

In S60 3rd Edition devices, a custom-created message is left in Outbox with status "waiting".

Description

This is a known issue that impacts all custom messaging applications, in other words, applications that create and send messages using the functions of CMsvEntry, TMsvEntry, and a client MTM.
This issue can be reproduced by creating and scheduling a message to be sent immediately. The message may be left in the Outbox with the status "waiting" for a period of time specified by the iDate member of your message entry's TMsvEntry object.

Solution

The solution to this problem is to set your TMsvEntry's iDate to the Universal Time (by calling iDate.UniversalTime()). The messaging server will calculate the difference between the local time and the (universal) time stamp of the message entry and schedule the entry accordingly.