-
Notifications
You must be signed in to change notification settings - Fork 16
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
fix(chat): offline msgs order #4794
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛳
message.payload.body.messages | ||
.sort((a, b) => a.createdAt - b.createdAt) | ||
.map(async (message) => { | ||
const stored = await iridium.connector?.dag.get( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can use iridium.load and skip the manual decryption step
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, maybe something about the structure of the payload. I'll take a look in a followup.
I am seeing weird issues where the offline messages don't come in consistently, or they will show up, then on reload they dissapear. Do you think this should be looked at in a follow up pr? Or maybe it works with your edit message pr, i will check that out now |
Those should not be related to these PRs, are you experiencing the same on dev? |
@molimauro I also tested this one as well and wanted to leave a little note of my findings. I was able to add friends and send messages from both sides and still not receive them on either side Screen.Recording.2022-09-14.at.1.47.31.PM.mov |
@phillsatellite i tried and they worked on my side but ill try to dig more |
fa54eb1
to
85ffdff
Compare
85ffdff
to
e53e517
Compare
I think the inconsistency should be addressed in recently merged branches. if not I will follow up on this. |
What this PR does 📖
Which issue(s) this PR fixes 🔨
Special notes for reviewers 🗒️
Additional comments 🎤
After this we can merge #4755 too