-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2024-11-26] [$250] Distance - After tapping split expense with amount button, briefly "split expense" button shown #52196
Comments
Triggered auto assignment to @jliexpensify ( |
Edited by proposal-police: This proposal was edited at 2024-11-07 16:12:46 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Distance - After tapping split expense with amount button, briefly "split expense" button shown What is the root cause of that problem?We reset the draft transaction on creating the expense and we show the App/src/components/MoneyRequestConfirmationList.tsx Lines 414 to 415 in 8a83e2b
so as the draft transaction amount is not available (0) it will show 'split expense' What changes do you think we should make in order to solve the problem?We can remove the draft transaction clearing code every where we are clearing it now like here Lines 4134 to 4136 in 8a83e2b
here here here Because we are already clearing the draft transaction in startMoneyRequest Lines 392 to 393 in 8a83e2b
We can apply the change for our split case related to the current issue but I think it is better to apply it globally. What alternative solutions did you explore? (Optional)Alternatively we can use
If we feel unsafe clearing the draft transaction before the create request actions have been called ( as we need the draft transaction value inside the functions) we can call it after the |
@FitseTLT @IuliiaHerets a few questions:
Do you mean 59-0 @IuliiaHerets?
Does this mean more than 1 other person? Is there a minimum number? |
@jliexpensify Yes, you are right, build - v9.0.59-0. |
Job added to Upwork: https://www.upwork.com/jobs/~021855539288770032834 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
Thanks for cionfirming - adding |
@FitseTLT Thanks for the proposal. The RCA and the solution look good to me. 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @Julesssss, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @FitseTLT 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.63-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-11-26. 🎊 For reference, here are some details about the assignees on this issue:
|
@s77rt @jliexpensify @s77rt The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
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: v9.0.59-0
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
After tapping split expense with amount button, briefly "split expense" button must not be shown before showing conversation page.
Actual Result:
After tapping split expense with amount button, briefly "split expense" button is shown before showing conversation page.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6657658_1730988489659.Screenrecorder-2024-11-07-19-29-40-188.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: