Strange tizen.alarm.getAll() behaviour

Strange tizen.alarm.getAll() behaviour

BY 05 Jul 2013 Web Application Development

Hi,

 
It looks like tizen.alarm.getAll() is reporting wrong alarm time.
Here is a sample code
tizen.alarm.add(newAlarm, "vrpbxib8us.fdsp", newAlarmArguments);
console.log("adding alarm "+JSON.stringify(newAlarm));
console.log(JSON.stringify(tizen.alarm.getAll()));

here is the console output :

wgt/js/main.js (209) :adding alarm {"daysOfTheWeek":[],"date":"2013-07-05T10:48:59.000Z","id":"263832","period":604800} 
wgt/js/main.js (212) :[{"daysOfTheWeek":[],"date":"2013-07-05T11:48:59.000Z","id":"263832","period":604800}]
 
Looks like 1 hour was magically added during the process. By the way, the alarm fires at the right time (ie 10:48:59 UTC).
But the problem is that if want to use the  date value of stored alarms for some processing in my app, I need to substract 1 hour, and i’m a bit worried about my code being broken in future tizen versions.
 
Regards,
 
P.S : I’m using 2.1 sdk and with a developper device.
 

 

 

 

Written by