-
Notifications
You must be signed in to change notification settings - Fork 541
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
[BUG] DATE PROBLEM #3145
Comments
Thank you @hkjansonchan for raising Issue #3145! 🚀 Tagging @ILIYANGERMANOV for review & approval 👀 |
@hkjansonchan can you please add more details/screenshots and the steps to reproduce the issue. This is how I tried to reproduce it. It is working as expected. issue_3145_not_repr.mp4 |
It's a timezone issue. Set your device to GMT+8 or some big difference from UTC and it'll break. We need to work everywhere with |
Same problem. The transaction history screen seems to be using the GMT+0 timezone no matter what. |
I'm on it |
Thank you for your interest @rishi2062! 🎉 If you don't want to work on it now, please un-assign yourself so other contributors can take it. Also, make sure to read our Contribution Guidelines. |
…nd in Transaction card details
…ansaction card details (#3212)
@ILIYANGERMANOV is this issue still open after my merge |
Please confirm the following
Describe the bug
I just input the date & time eg 18 May 7.00am
But after I confirmed the date become 17 May and I press in it, It was 18 May 7.00am
That's weird
To Reproduce
Expected behavior
No response
Screenshots
No response
App version
4.6.3(163) from Play Store
Smartphone
Samsung Galaxy A54
Additional context
No response
The text was updated successfully, but these errors were encountered: