This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IOS Calendar showing in 24 hour format

Hello!

Has anyone found a way to stop the Calendars in the mobile app from showing in 24 Hour format? When you open the meeting it shows it in 12 hour, but the actual Calendar itself is in 24 Hour format.

Thanks!

This thread was automatically locked due to age.

0 Haridoss Sreenivasan over 6 years ago

Hi Peter,

This works for me on an English iPhone where SSE is connected to our Exchange Server at Sophos (company phone).

Please help me with the following information to assist you better:

1. Which language and localization settings are set on the iOS device?
2. Where is the calendar hosted?
3. What is the Exchange / Lotus Traveller version?

Haridoss Sreenivasan
Technical Support Engineer | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 Peter Schnick over 6 years ago in reply to Haridoss Sreenivasan

1. Which language and localization settings are set on the iOS device? English. Region - Canada. Calendar - Gregorian
2. Where is the calendar hosted? On Exchange and on the phone, when opening the app the time format is 24 hour. If I open the calendars that are not in Sophos they are in 12-hour format.
3. What is the Exchange / Lotus Traveller version? Exchange 2013
Cancel
Vote Up 0 Vote Down

Cancel
0 Peter Schnick over 6 years ago in reply to Peter Schnick

Any suggestions for this?
Cancel
Vote Up 0 Vote Down

Cancel
0 Peter Schnick over 6 years ago in reply to Peter Schnick

I updated the client to the new version, the calendar is still in 24 hour format.
Cancel
Vote Up 0 Vote Down

Cancel
0 Peter Schnick over 6 years ago in reply to Peter Schnick

Working with support we resolved this issue.

Had to remove the application and install it again fresh. The in-place upgrade did not resolve the issue.
Cancel
Vote Up 0 Vote Down

Cancel