Time zone behavior

[werebus]

We've had 2 or 3 reports of times being incorrect -- off by 3 or four hours. We're pretty sure it's related to the local time zone on the device. At least one user said they had definitely been to California within the last few days. Although, confusingly, they checked their time zone settings and they were correct (GMT-0500). Is there something in our app that is holding on to stale time zones?

We discussed it over in umts/BusInfoBoard#62, and it's arguable that using the device time is "correct", but should we be sanity-checking the user's time zone against their location? Against the stop location?

[mboneil10]

@artarazavi said she's going to look into this

[akaplo]

Might be worth checking where times are wrong - if it's Plan Trip, likely a Google problem, a Map page could be us or Avail (more likely Avail) and a Departures page could be us or Avail (50/50).

If it's us, it's probably something momentJS related?

[werebus]

I could only find two reports in my email, although one of them referenced a third.

• In one, they clearly showed a screenshot of the Amherst Post Office stop page. However, they never got back to me about what OS they were running. It's hard to tell from the screenshot.
• In the second, they didn't say where in the app the issue was, but did say they were running a Moto Z, Android 7.1.1.

Here's the text of the two reports I could find:

---

(2017-09-29)

Hi,

I have installed and reinstalled app multiple times but I'm seeing the issue continuously. The app is not displaying me the buses properly. The time for the bus is messed up.

Attaching a screenshot.

---

(2018-01-27)

I traveled to the West coast and came back to EST. Somehow the timings are wrong on the app. It is still 3 hours behind on the schedule. I find it odd as I cleared the cache, uninstalled, reset my phone timings and nothing seem to fix it.

I am using a Moto Z play with Android 7.1.1

My timezone is GMT -500. I have also tried with network provided time zone.