Bug: UserActivity.startTime incorrect

I did run the the following test:

while (sample != null) {
var startTime = sample.startTime.value();
System.println("startTime "+startTime);
var correctedStartTime = (startTime+631065600); // in seconds
System.println("correctedStartTime "+ correctedStartTime);
var now = Time.now().value();
System.println("now "+now);
System.println("duration: " + (now-correctedStartTime));
sample = userActivityIterator.next();
}

And indeed the last item is the most recent 

And indeed the difference is +631065600

startTime 1051904761
correctedStartTime 1682970361 --> 01/05/2023, 21:46:01
now 1682970387 -- > 01/05/2023, 21:46:27
duration: 26

But that's also incorrect see my response to Jim then I end up with 09/03/2023. 

The simulator by the way gives an 2021 date and using the Garmin epoch (add the 631065600) gives a negative number some kind of role over? Very odd. 

He's off by 20 years, because Garmin epic is 1990.

You should use the Garmin SDK's functions, as the timestamp is Garmin Epoc, not Unix timestamp...

Using Timestamp Converter.

Someone just mentioned it is incorrect in the info (Bug: UserActivity.duration incorrect type?? - Connect IQ Bug Reports - Connect IQ - Garmin Forums here where I also posted). I was trying with this code as workaround for the the bug about the sample.duration.

He gave the info Cookbook | FIT SDK | Garmin Developers

But still than adding 631065600 results in 1678396225 that also results in 09/03/2023, 22:10:25.

It should be 30-04-2023 18:10  or Gregorian 1682871000 according tot the information on my phone.

How are converting the number into a date/time? Converting the Unix time to a Moment than using Gregorian.Info?

Are you off by your UTC offset in what you are doing now?