[TIMOB-23392] Analytics: Timestamp for Windows payloads are inconsistent with other platforms

GitHub Issue	n/a
Type	Improvement
Priority	High
Status	Closed
Resolution	Fixed
Resolution Date	2016-05-20T13:49:12.000+0000
Affected Version/s	Release 5.3.0
Fix Version/s	Release 5.4.0
Components	Windows
Labels	Analytics, qe-5.3.0, qe-5.4.0
Reporter	Harry Bryant
Assignee	Christopher Williams
Created	2016-05-17T17:18:10.000+0000
Updated	2016-07-07T18:24:55.000+0000

Description

When comparing the payloads for the Windows platform to android / iOS, it was found that the timestamp is not consistent with the other platforms: *Windows:* ts: "2016-05-16T18:51:13.488Z” *Android / iOS:* ts: "2016-05-13T21:32:50.228+0000” Phones were verified to have the correct time configured prior to obtaining the payloads.

Steps to Reproduce

1) Install a titanium project on a windows phone device 2) Launch the app 3) Use either - a) point device to staging via DNS setting, check logs. b) Use get last event api c) If you have backend access, check the raw event on AWS. 4) Examine any of the standard event types.

Actual Result

Windows timestamp is different from other platform timestamps.

Expected Result

Windows timestamp should be consistent with the other platform timestamps.

Comments

Christopher Williams 2016-05-18

https://github.com/appcelerator/titanium_mobile_windows/pull/704 Basically it boils down to us using the ISO string format and the other platforms using a "+0000" timezone offset instead of "Z" at the end. So I generate our ISO string and replace "Z" with "+0000".
Harry Bryant 2016-07-07

Verified as fixed, Timestamp for windows platform is now consistent with iOS / Android. "ts": "2016-07-07T18:08:30.304+0000", Tested On: Windows Phone 10.0 (Microsoft Lumia 640 LTE) Windows 10 Pro Ti SDK: 5.4.0.v20160705213725 Appc Studio: 4.7.0.201606220541 Appc NPM: 4.2.7-2 App CLI: 5.4.0-26 Xcode 7.3 Node v4.2.6 *Closing ticket.*

JSON Source