×
Namespaces

Variants
Actions
Revision as of 03:45, 19 June 2012 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

From Nokia Developer Wiki
Jump to: navigation, search

Archived.pngArchived: 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
S60 3rd Edition (initial release)
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.

This page was last modified on 19 June 2012, at 03:45.
39 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×