Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Archived:WMA implementation for getTimestamp() returns always null on S60 3rd Edition initial release (Known Issue)

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

Article Metadata
Created: User:Technical writer 1 (22 Feb 2007)
Last edited: hamishwillee (24 Jul 2013)


JSR-205 defines a method getTimestamp(), which is applied to a message and it indicates when the message has been sent (see JSR-205, page 16). According to JSR-205, this method might return "null if the timestamp is not set or if the time information is not available in the underlying protocol message". However, the S60 WMA implementation returns always null as when calling getTimestamp() and this might create problems for MIDlets if the result of the getTimestamp() method is not checked against the null value.

How to reproduce

Call getTimestamp() for a received MMS. It will return null.


This problem is corrected in S60 3rd Edition, FP1. Note that Java applications should be prepared for the situation when the getTimestamp() function returns null (the most common mistake found in MIDlets is that they simply call the getTimestamp().toString() method without checking the result of the getTimestamp() method against null in beforehand).

This page was last modified on 24 July 2013, at 04:40.
17 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.