-
Notifications
You must be signed in to change notification settings - Fork 240
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
TemporalDateTime wrong on each device #4492
Comments
Hi @harrynguyen2510, I understand you're seeing inconsistent ordering of messages in your app. It's unclear to me how you are sorting them. What value you are sorting by? By what method? Also what do you mean by |
Hi @Equartey thanks for reply, I have updated the Datastore content board image above, please take a look at it. It's high chance that the root of issue is from TemporalDateTime when creating message |
any update? |
@harrynguyen2510 can you fill out the reproduction steps section in the issue template? Thanks |
@harrynguyen2510 if you are still facing this issue please fill out the reproduction steps in the issue template. Thanks. |
Description
I'm building a chat app and having issues about timing of message
Here is the function to create message
As you can see I get
TemporalDateTime.now()
to take UTC date time on current device then upload to Amplify Datastore,When I open Datastore content board, sort list of messages in latest-oldest order to observe the timing of message uploading
I found message of phone A, time upload is right, because new message adding to the board is on top, but not for B, message from B is added somewhere below (even B sent message after A)
A Quick notice that, messages from A is formed together in order on board, while B has formed as well, but this doesn't alway happen
This issue results in like this:
For example, from
Categories
Steps to Reproduce
No response
Screenshots
Platforms
Flutter Version
3.19.1
Amplify Flutter Version
12.10.1
Deployment Method
Amplify CLI
Schema
The text was updated successfully, but these errors were encountered: