desktop: Time is incorrect in OSX High Sierra
I confirm (by marking “x” in the [ ] below: [x]):
- This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
- This doesn’t reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
- I have read contributing guidelines.
https://mattermost.atlassian.net/browse/MM-14168
Summary
The time of the desktop app in mattermost is incorrect in High Sierra. This may be related to daylight savings time.
The time is correct in the web browser, and was correct before upgrading from El Capitan.
Steps to reproduce
Operating System: OS X High Sierra: 10.13.2 (17C88)
Mattermost Desktop App version: Version 3.7.1
- Set your system timezone to a city that is currently experiencing daylight savings time, such as Melbourne - Australia
- Write a message to someone
Expected behavior
The time displays the correct time.
Observed behavior
The time is one hour out:
Possible fixes
No idea!
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 28 (13 by maintainers)
Hello, Should I open an issue for Windows and Linux version? Because we have same issue at Windows and Linux desktop version 4.1.2. At Mattermost web, time is correct. We are using Mattermost server version 5.1.1 and date time in OS is ok.
@jasonblais @yuya-oc As you can see from the following screenshot, hovering over the text 6:15 PM shows the correct time 5:15 PM === 17:15! So it’s just adding an hour somehow before displaying the text.
Please check the fix for mobile version, maybe it’s the same issue: https://github.com/mattermost/mattermost-mobile/pull/1982
I had the same issue on both desktop and mobile, it just have been fixed yesterday in Android: https://github.com/mattermost/mattermost-mobile/issues/1935
Please take a look for a fix for desktop too!
@yuya-oc, Yep, appears to be that function is incorrect in Electron. Do you want me to raise an issue with them?
Edit: I’ve managed to reproduce it with the quick start, so I’ve gone ahead and raised an issue.