I am writing an app that gets the PIM data from the phone and sends it to a server. To do this I use PIM.toSerialFormat() that will write data PIM entry to an output stream which I then send to the server. I then can retrieve the PIM data at a later late from the server and write it to the phone. This all works fine. The problem is that when I get the PIM data from the todo list (and possibly the event list, I haven't checked) and write it to the output stream the date that was for the todo task changes to the current time and date of the phone. So therefore when I read the todo task back from the server it will have the wrong scheduled time.
For example; I have a todo task scheduled to go off on the 20-9-07 at 20:00. When I send the todo task to the server the scheduled time changes to the time and date the device is currently at, say 13-9-07 14:53. So when I get the data back from the server and save the todo task on the device the time for the scheduled task is now 13-9-07 14:53
Has anyone noticed this? Is there a work around? I really hope this is not a bug in the PIM api. I think it is a serious one! At the moment I think the only work round would be to read from the pim entry and not us toSerialFormat
Uh-oh. I'd check with Nokia Developer Support if I was you.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.