Expensify
Chat - Main chat opens when add reply on deleted parent message
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.55-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Email or phone of affected tester (no customers): [email protected] Issue reported by: Applause - Internal Team
Action Performed:
- Go to any chat
- Send a message
- Add a reply the the message
- From the thread page delete the parent message
- Add new reply
Expected Result:
User should remain on thread page when add new reply
Actual Result:
User navigates to main chat when add reply on deleted parent message
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- [ ] Android: Standalone
- [ ] Android: HybridApp
- [ ] Android: mWeb Chrome
- [ ] iOS: Standalone
- [ ] iOS: HybridApp
- [ ] iOS: mWeb Safari
- [x] MacOS: Chrome / Safari
- [ ] MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/user-attachments/assets/e5d6e179-b6b6-44ef-9817-e82b8380ec90
Triggered auto assignment to @jliexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
![melvin-bot[bot] avatar](https://avatars.githubusercontent.com/in/179547?v=4 "Published by a pub.dev verified publisher"){kind=small}
This is BE bug the BE is deleting isDeletedParentAction on ADD_COMMENT
"message": [
{
"html": "",
"text": "",
"type": "COMMENT",
"whisperedTo": []
}
and it will set it back on OPEN_REPORT
I can repro this one. Going to bring it to #quality to see if someone can pick this up
EDIT: Posted.
@jliexpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
@jliexpensify this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
@jliexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
@jliexpensify Huh... This is 4 days overdue. Who can take care of this?
@jliexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
@jliexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
@jliexpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
@jliexpensify 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
@jliexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!