UserProfile.getUserActivityHistory() startTime weird results

I think this is an issue that's come up before. Internally, FIT activity file timestamps are based on the Garmin epoch (midnight, Dec 31, 1989), and there's some cases where the Garmin API fails to convert this to the standard UNIX epoch ¯\_(ツ)_/¯.

[https://developer.garmin.com/fit/cookbook/datetime/]

The FIT Profile defines the date_time type as an uint32 that represents the number of seconds since midnight on December 31, 1989 UTC*. This date is often referred to as the FIT Epoch.

Sounds like they are in "Garmin Time" vs "Unix Time".  Search the discussion forum and the bug report form for "Garmin Time" as there are work arounds, and then do a bug report.

Here's a bug report from a few months back about the exact same thing:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/wrong-time-stamp-with-useractivity-starttime

I'll point out that this type of bug has happened more than once. Here's a report from 6 years ago (which was fixed):

https://forums.garmin.com/developer/connect-iq/f/discussion/4555/devices-position-info-when-is-in-garmin-time-and-not-utc

It's funny how the same classes of bugs recur over and over again.

Somehow related question; when I get userActivities it starts from oldest to newest. Isn't it possible to turn that around? Can't find something in the docs for this. I'm only interested in the newest ones.

Unfortunately, I don't think there is.

You could always use a helper function to grab the data you want:

// n: number of items to retrieve from the end of an iterator
// iterator: a newly initialized iterator (for which next() hasn't been called yet)
//
// Returns last n items of iterator in an array, from earliest to latest
// (if there are less than n items in the iterator, all of them are returned)
function getLastNItemsFromIterator(n, iterator) {
    // circular queue to store last n items
    var queue = new[n];
    var queueIndex = 0;
    var numItems = 0;

    var item = iterator().next();
    while (item != null) {
        queue[queueIndex] = item;
        queueIndex = (queueIndex + 1) % n;
        item = iterator().next();
        numItems++;
    }

    var numItemsToReturn = (numItems > n) ? n : numItems;
    if (numItemsToReturn < n) {
        queueIndex = 0;
    }

    // return last numItemsToReturn items in order
    var output = new[numItemsToReturn];
    for (var i = 0; i < numItemsToReturn; i++) {
        output[i] = queue[(queueIndex + i) % n];
    }
    return output;
}

Oh yes I'm doing something similar now. But I hoped to avoid looping over them all. Thought there would be a similar way like getBodyBatteryHistory() where we can add an order in the options.

Did you find a way to loop from the newest?

Nope :/ Not ideal