All Day Events showing up on wrong day in Calendar

8 postsstarted by mnmpeterson 3,350 viewsoriginal topic

#1
I noticed with the new version that the calendar is showing an event in Wednesday that is an all-day event for Thursday. It looks like all All-Day events are displayed in the day before they occur.
Community Administrator
#2
I don't see that on my calendar. I notice that you're in Arizona. Since AZ doesn't follow daylight savings, I wonder if there's a problem with the timezone settings. I'd have a stake person check the time zone for each of your locations and make sure it's set to "Phoenix" and not "Denver" (Same time zone, different daylight savings).
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
#3
The calendar entries show up correctly in the online calendar. They just don't show correctly in the LDS Tools app. The entries are not tied to any location so that couldn't be the problem. But DST might be an issue since Arizona doesn't observe DST.
Community Administrator
#4
Can you check and see if the problem is there for events outside of DST?
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
New Member
#5
LDS Tools now looks great but still has problems like updating the calendar correctly
I now have the 12 months I typed in as Stake Admin
and see you can subscribe or unsubscribe sub folders
but some sunday events are on Saturday and other events
do show up on previous or later days
Southern California
#6
I checked and it happens for events outside of DST.
New Member
#7
I am having that issue as well and this has been confirmed with others here in our Stake when they update to version 2.0 on their iPhones. We are in NZ with GMT+12
#8
I sent an email to the iOS support team, and their reply was that they are aware of the problem, and that their developers are looking into it.