-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Duplicate Messages appearing in compose box after message sent (then app closed soon after) #11293
Comments
Surely we have already logged this somewhere...? It's the same bug that will be fixed by |
What's different for this, or what I hadn't experienced is the duplicate is in the compose box. Updated title
https://github.com/Expensify/Expensify/issues/227234 I'd assign to myself to monitor or test once the time is right but I'm OOO for a month soon |
Triggered auto assignment to @Christinadobrzyn ( |
Since this is on hold until https://github.com/Expensify/Expensify/issues/227234 is resolved, going to move this to weekly |
Moving to weekly since this is on [Hold] |
This is probably the same thing, but I can consistently reproduce it with the following steps:
Weirdly this doesn't happen to me with any message, but with this specific content it does. |
I can replicate that in staging.
So should this stay on hold for this? https://github.com/Expensify/Expensify/issues/227234 I'm not really sure what to do here... |
Yeah.. I'd recommend keeping it on hold pending #227234 in E/E. It'll be addressed there. As far as the BZ role here.. I'd stay on top of the tracking issue and, if progress isn't being made, ping the folks assigned there. |
Still on hold waiting for - https://github.com/Expensify/Expensify/issues/227234 |
Stil tracking https://github.com/Expensify/Expensify/issues/227234 |
Stil tracking https://github.com/Expensify/Expensify/issues/227234 |
Just came across this one. I'm taking over since I'm on the linked Sequence Numbers doc. |
Still on hold for sequence numbers, which is starting to pick up the pace. |
Same same, though we're making great progress. |
Still on hold for the sequence numbers. |
Looks like something related to As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our Feel free to drop a note in #expensify-open-source with any questions. |
Taking this off hold now and attempting to reproduce. |
Unable to reproduce this one now. Closing. |
This issue used to happen to me frequently, not able to reproduce on two tries either! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
No duplicated messages should appear
Actual Result:
Multiple messages appear in the conversation
Related issues:
#10615
#10550
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.3-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
[duplicates at startup.txt](https://github.com/Expensify/App/files/9649237/duplicates.at.startup.txt) [scroll to make duplicate message.txt](https://github.com/Expensify/App/files/9649238/scroll.to.make.duplicate.message.txt)
2022-09-22_11-49-55.mp4
Expensify/Expensify Issue URL:
Issue reported by: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1663776833139009?thread_ts=1663714013.290919&cid=C01GTK53T8Q
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: