Wait, what?!?

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.

@plusgut mmm maybe was date (wrongly formatted) + 6 months?

@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.

True

@Jop- yes

Time machine?

@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).

@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?

@plusgut
Here is milliseconds to date but value is in seconds.

@plusgut
And here's when it is actually in milliseconds

Uh! Thanks! I'm so bad at math :D

@plusgut
But yeah, it is still jan 1970 not july 😅

Then you totally have a point in your theory, good one!

@sudani93 true, but that's good thinking and would be a possibility to invest in that corner, if you had to debug it.