Just a quick update on the whole TripIt debacle.
The TripIt support team were very good in responding to the problem. While I didn’t get any money back, they didn’t throw me any legalese/boilerplate response, and took the issue seriously. Kudos to Ruth, the support rep who was my primary contact, for handling this well.
They responded by offering me an upgrade (worth $49 in $$ terms, but pretty useless to me in the context of what has happened, as the primary issue is the fact I no longer feel like I can trust the application) and looked into the matter.
The first suggestion was this was a daylight savings issue with my phone, (as a few folks have suggested to me personally or via Twitter) but I pointed out this didn’t seem to make sense because:
- The earlier flight on the same day is also displayed as AEDT and this is displaying correctly as 6:15am (as per the web-based application).
- The support team asserted that “in Australia and on April 3, 2011, Daylight Savings Time ended and I believe because the last flight (Virgin Blue 885) coincided with that date”, which was incorrect. The flight was for April 2 at 7:15pm and flight time was 1 hr and 15 mins, meaning I would have arrived in Sydney before 9pm on April 2. DST didn’t end here in Australia until 2am on April 3, well outside the range of that particular flight.
- Even if the flight did cross timezones, the departure time should reflect the timezone of departure, not the destination, so this still should not have happened.
- I confirmed the bug in both Melbourne under daylight savings (when the error occurred) and in Sydney (upon arrival the following day) outside of daylight savings â€” which suggests that it was not an issue with the settings on the phone, as the problem should not have exhibited before or after the timezone change, according to this explanation, but it clearly occurred in both timezones.
After this response, the team looked into it further and found:
It appears that in our system, for Melbourne, Australia, our system had the April 2 date listed as the end of Daylight Savings Time for EST.
I’ve immediately filed a ticket with our engineers to make sure that daylight savings time is properly picked up for Melbourne to fix this issue going forward. I’m also having our engineers double-check all timezones in Australia.
So the issue was confirmed as a daylight savings issue, but not related to my phone or setup.
While I still don’t think that particular finding fully explains the issue (if it clicked over on April 2 instead of 3, why was the first flight time on the same day correct?). But at least I’m glad that identifying the issue may avoid future issues for other TripIt users.