Recent Update to Calendar Timezones is Broken

James,

Just to confirm, you have your device set to Eastern time. When you look at the calendar in Scoutbook, the events that should be display at, for example 7:00 PM are displaying at 6:00 PM.

When you edit the event, does it also show as 6:00 PM?

No. Events we had created prior to the “update” now appear an hour earlier in the scoutbook calendar, but reminder messages and my synced google calendar show the correct time.

If I now create an event in scoutbook, the calendar will show whatever time I now set, and reminders appear to be correct.

It’s almost as if events already in scoutbook at the time of the update were pushed left an hour, but only when viewing the calendar in scoutbook itself.

1 Like

I’m stumped. It sounds like the meetings were successfully converted to ET, but then the devices thing they should be CT. Is there any difference between newly created events and existing events?

Is there anything unique about IN time? Is the entire state on Eastern Time? The state observes DST?

Great job Scoutbook developers for fixing the issue as of 11/7/19!

1 Like

I’m in the same pack as @jamesdesaulniers and we do have some people that have the correct times, while most others do not. I am one of the ones that has it wrong and our ACM has it correct. This is very problematic as our users are seeing incorrect times. This is a direct result of the conversion.

The entire state does not follow DST…

How has the issue been fixed?

The OP had a slightly different issue than you are seeing. Several timezone fixes went in today, but I don’t think any would impact you.

Do you mean part of the state observes DST? Or none of the state observes DST? If part, how close are you to that line.

Indiana is a mix of Eastern and Central time. Time zones break by, IIRC, county line, but the zip codes don’t.

1 Like

We aren’t close at all to the non-DST people.

I’m not sure if it has been mentioned already, the user’s date time group setting in his/her device must be correct. Also if one made a correction or update on the date and time settings, it’s good practice to restart the device to insure the applicable apps and programs uses the updated date time group.

1 Like

Here are screen grabs of Scoutbook and the same synced calendar in Google. Time in Google is correct.Fullscreen_11_7_19__4_22_PM

I don’t use Google calendar, but the Scoutbook calendar of event is the first basis of correct date/time. Assuming device setting is correct, I suggest looking into the Google calendar time settings, if there’s such thing. Maybe there is a DST switch/toggle difference; I keep my device settings to automatically synchronized with Internet “time.window.com

The time in Scoutbook was accurate before the conversion this month.

When events are emailed out we are getting 2 emails. One with the correct time (PST) and one with the times 2 hours ahead.

Jumping back in because This Isn’t Funny.

Organizing 7 units, covering 5,000+ for Scouting for Food was boondoggle start. Some of the parents saw 9:00am meeting time and the others saw 10:00am meeting time. Two of them literally standing side by side with two phones, with two different start times. They showed me their screens.

Please fix this.
Really.

Were the phones showing the same current time? Scoutbook uses the device time zone to display the times on the calendar.

is There any pattern with the devices that show it correctly or incorrectly?

Hi - jumping in with some information.
We are also seeing the problem, and it’s causing confusion.
Here is what I have collected:
Showing wrong time in scoutbook.com events listing:

  • Windows 10 laptop (sets time with NTP + manual timezone setting, MST in this case)
  • Android 9 phone (sets time automatically “network provided time”)

Showing correct time in scoutbook.com events listing:

  • Chromebook (sets time automatically “use IP address to determine location”)
  • iPhone (don’t know how iOS sets the time)

We also have seen double email notifications (one correct one wrong)
All devices were showing the correct local time.