Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timestamp is off by -1 hour #1181

Closed
2 tasks done
busches opened this issue Apr 15, 2019 · 6 comments
Closed
2 tasks done

Timestamp is off by -1 hour #1181

busches opened this issue Apr 15, 2019 · 6 comments

Comments

@busches
Copy link

busches commented Apr 15, 2019

My Setup

  • Operating System: Windows 10
  • App Version: 2.15.1
  • Installation type: exe
  • I have tested with the latest version
  • I can simulate the issue easily

Description

When viewing Rocket.Chat in the Electron Desktop app, all timestamps are off by -1 hour. e.g. If it's 11:32 AM, I see everything as 10:32 AM. If I load the server in the browser, on the same computer, I correctly see it as 11:32.

Current Behavior

Timestamps are off by -1 hour

Expected Behavior

Timestamps use current computer time.

I have uninstalled/reinstalled. I checked remove user data and even manually removed AppData/Roaming before installing. The issue started around the time Daylight Savings time went into effect. I've also traveled to another timezone and the timestamps worked then, but reverted back to -1 once I returned to my normal timezone. No other users on this server have reported this issue.

@tassoevan
Copy link
Collaborator

May I ask you in which timezone you are?

@busches
Copy link
Author

busches commented Apr 18, 2019 via email

@paulopera
Copy link

We are having the same issue with the macOS App V 2.16.0 but in the web app the hour is correct at least in Chrome. It shows +1 hour and our timezone is GMT-3.

@tassoevan
Copy link
Collaborator

@paulopera The origin of this bug lies on Node: nodejs/node#30211
It's affecting all Electron-based apps (including desktop apps for Slack, Discord, Mattermost etc.) and there is no known workaround for now. We'll patch our app as soon as there is a fix for it.

@paulopera
Copy link

@tassoevan Thanks for reaching out and hope they could fix the problem.

@jeanfbrito
Copy link
Collaborator

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants