-
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
[Offline] Group chat - Group chat turns to not here page when creating group with non-existing account #51473
Comments
Triggered auto assignment to @mallenexpensify ( |
@mallenexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
Edited by proposal-police: This proposal was edited at 2024-10-27 14:23:02 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Group chat - Group chat turns to not here page when creating group with non-existing account What is the root cause of that problem?It shows 404 page not found because we did not pass the emailList value when requesting to the OpenReport API after change from offline to online App/src/pages/NewChatConfirmPage.tsx Lines 101 to 108 in 652d2ff
After this PR #51093 we will replace duplicated OpenReport requests if the request.command and the report id is equal meaning it will replace the previous request with the new one (when opening group chat) which will remove the emailList value (from the previous request createGroup)App/src/libs/actions/Report.ts Lines 982 to 983 in 652d2ff
What changes do you think we should make in order to solve the problem?We should check also for API.paginate(CONST.API_REQUEST_TYPE.WRITE, WRITE_COMMANDS.OPEN_REPORT, parameters, {optimisticData, successData, failureData}, paginationConfig, {
checkAndFixConflictingRequest: (persistedRequests) =>
resolveDuplicationConflictAction(persistedRequests, (request) => request.command === WRITE_COMMANDS.OPEN_REPORT && request.data?.reportID === reportID && request.data?.emailList === parameters.emailList),
}); ResultScreen.Recording.2024-10-27.at.07.20.52.movWhat alternative solutions did you explore? (Optional) |
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
@NJ-2020 thanks for the proposal. I'm unsure exactly what I want to do with the issue so I added |
Okay no problem, thank you |
I'm back from OOO on Nov 14th, not assigning another BZ, if one is needed please add or post in #contributor-plus to ask for one to be added, thx. |
Just spent 20 mins trying to get into new.expensify.com and staging.new.expensify.com with my [email protected] account and had no luck with both, will revisit/test soon |
This has been fixed here #52350 cc: @mallenexpensify |
Thanks @NJ-2020 , throwing |
Issue not reproducible during KI retests. (First week) |
Looks like it's fixed 🎉 (also... 🌮🌮🌮🌮🌮) |
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.54-1
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:
Expected Result:
Group chat will not turn to not here page after returning online
Actual Result:
Group chat turns to not here page after creating group chat with non-existing account offline and returning online
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6645533_1729859324388.20241025_201912.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: