starred/SMSSync

Fork 0

mirror of https://github.com/ushahidi/SMSSync.git synced 2026-04-26 00:05:57 +03:00

[GH-ISSUE #179] sent_timestamp is not unix time format compliant #134

New issue

Closed

opened 2026-02-28 01:23:21 +03:00 by kerem · 7 comments

kerem commented

2026-02-28 01:23:21 +03:00

Owner

Originally created by @redbullpeter on GitHub (Jun 22, 2014).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/179

The sent_timestamp that is being sent is not in the correct unix time format.

For example the time returned today was: 1403438526000
If you convert this strictly, assuming 64 bit time stamp, then the date would be: 13/03/46443 11:00:00 GMT

The time stamp should actually be: 1403438526
Which converts to: 22/06/2014 12:02:06 GMT

Millisecond accuracy should be represented as 1403438526.000

Originally created by @redbullpeter on GitHub (Jun 22, 2014). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/179 The sent_timestamp that is being sent is not in the correct unix time format. For example the time returned today was: 1403438526000 If you convert this strictly, assuming 64 bit time stamp, then the date would be: 13/03/46443 11:00:00 GMT The time stamp should actually be: 1403438526 Which converts to: 22/06/2014 12:02:06 GMT Millisecond accuracy should be represented as 1403438526.000

kerem closed this issue

2026-02-28 01:23:21 +03:00

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@kkanigowski commented on GitHub (Jul 7, 2014):

@eyedol, Is this timestamp still a problem ? If it is necessary, I will convert it to unix timestamp.

@kkanigowski commented on GitHub (Jul 7, 2014): @eyedol, Is this timestamp still a problem ? If it is necessary, I will convert it to unix timestamp.

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@mandric commented on GitHub (Jul 7, 2014):

How hard is it to do timestamp/1000 if you want a unix timestamp (seconds from epoch) with a decimal for ms? I see no reason to change this, it would require all servers to update their code, if anything just change the documentation to state the timestamp is milliseconds from epoch.

@mandric commented on GitHub (Jul 7, 2014): How hard is it to do timestamp/1000 if you want a unix timestamp (seconds from epoch) with a decimal for ms? I see no reason to change this, it would require all servers to update their code, if anything just change the documentation to state the timestamp is milliseconds from epoch.

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@KamilKalfas commented on GitHub (Jul 9, 2014):

@eyedol I think that both of us agrees with Milan. There is no need to make such change on client side. In this case it's not a valid issue.

@KamilKalfas commented on GitHub (Jul 9, 2014): @eyedol I think that both of us agrees with Milan. There is no need to make such change on client side. In this case it's not a valid issue.

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@eyedol commented on GitHub (Jul 12, 2014):

@KamilKalfas I agree. We don't even have control over that value

@eyedol commented on GitHub (Jul 12, 2014): @KamilKalfas I agree. We don't even have control over that value

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@mandric commented on GitHub (Jul 12, 2014):

In the future if the timestamp from Android API changes we might introduce a function so we can maintain the ms from epoch format as a standard value. @redbullpeter I think we can close this issue ?

@mandric commented on GitHub (Jul 12, 2014): In the future if the timestamp from Android API changes we might introduce a function so we can maintain the ms from epoch format as a standard value. @redbullpeter I think we can close this issue ?

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@sorinpohontu commented on GitHub (Apr 21, 2015):

@eyedol I think you can close this issue for 2.8.0.

@sorinpohontu commented on GitHub (Apr 21, 2015): @eyedol I think you can close this issue for 2.8.0.

kerem commented

2026-02-28 01:23:22 +03:00

Author

Owner

@emerick-pro commented on GitHub (Mar 18, 2018):

Hello !
I am sorry to raise the issue when this was closed. I am having the issue of the timestamp from Android SMSSync that is always the same value (2147483647). I am building the application using PHP

 $sent_timestamp = (int) $_POST['sent_timestamp'];
 $event['event'] .='Bwarungitswe saa  : '.$sent_timestamp/1000;

And every time I am receiving the same value. 2147483647. Can you please help to figure out the cause or the solution?

@emerick-pro commented on GitHub (Mar 18, 2018): Hello ! I am sorry to raise the issue when this was closed. I am having the issue of the timestamp from Android SMSSync that is always the same value (2147483647). I am building the application using PHP ``` $sent_timestamp = (int) $_POST['sent_timestamp']; $event['event'] .='Bwarungitswe saa : '.$sent_timestamp/1000; ``` And every time I am receiving the same value. 2147483647. Can you please help to figure out the cause or the solution?

kerem referenced this issue

2026-02-28 01:24:22 +03:00

[PR #134] [MERGED] Add ability to build different flavors. one with analytics support or wi... #377