74
Comments
  • 8
    The developer made a until-date, but didn't give it a actual value and because of that the not existing value got casted to 0. And 0 is the unix-timestamp for 1.1.1970.
    Why the date is 6 months later? I would need to look into the actual code.
  • 0
    @plusgut mmm maybe was date (wrongly formatted) + 6 months?
  • 1
    @naghen yes probably, I guess the code should check if it's longer then 6 month from now into the future. But the now fuction doesn't do it's job as supposed. But that's just a lucky guess I'm doing.
  • 1
  • 0
    @Jop- yes
  • 0
    Time machine?
  • 0
    @plusgut
    Maybe the code uses milliseconds but the value it got for max Date is in seconds (long). Especially if the check depends on server time (and not device time).
  • 0
    @sudani93 I can't follow your train of thought. Why would it be that result, if the value is in miliseconds instead of seconds?
    When it's just of by a thousand it should not be exactly at 1970. Or what am I missing?
  • 1
    @plusgut
    Here is milliseconds to date but value is in seconds.
  • 1
    @plusgut
    And here's when it is actually in milliseconds
  • 1
    Uh! Thanks! I'm so bad at math :D
  • 0
    @plusgut
    But yeah, it is still jan 1970 not july 😅
  • 0
    Then you totally have a point in your theory, good one!
  • 1
    @sudani93 true, but that's good thinking and would be a possibility to invest in that corner, if you had to debug it.
Add Comment