-
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
[Paid] [HOLD for payment 2023-10-31] [$500] [HIGH] [P2P ACTIVATION] GBR is not shown when a pending payment is waiting on the user to enable their wallet #30033
Comments
Triggered auto assignment to @lschurr ( |
Bug0 Triage Checklist (Main S/O)
|
I'll take over the BZ on this one. CC: @samh-nl @akinwale as we're discussing in this thread. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Add a green brick road indicator What is the root cause of that problem?Missing check What changes do you think we should make in order to solve the problem?In OptionRowLHN we should add a condition here:
What alternative solutions did you explore? (Optional) |
Let's also fix the double message coming from here: https://expensify.slack.com/archives/C01GTK53T8Q/p1697796531033319?thread_ts=1697788964.150409&cid=C01GTK53T8Q |
ProposalPlease re-state the problem that we are trying to solve in this issue.GBR is not shown when a pending payment is waiting on the user to enable their wallet What is the root cause of that problem?We have written a condition to show the GBR if there is any action needed from the user here in this line Line 1287 in ca51f6f
But if see the condition it's going to be false in case What changes do you think we should make in order to solve the problem?We need to update the condition here Line 1287 in ca51f6f
if ((report.hasOutstandingIOU || report.isWaitingOnBankAccount) && report.ownerAccountID === currentUserAccountID) {
return true;
} In this way if the user doesn't had setup a wallet we show GBR. What alternative solutions did you explore? (Optional)NA For Double System Message#30033 (comment) Starting from the RCA from this comment. As Vivek suggested we need to stop rendering the reportAction. const shouldHideAction = originalMessage.type === CONST.IOU.REPORT_ACTION_TYPE.PAY && props.action.actionName === CONST.REPORT.ACTIONS.TYPE.IOU; The above lines does check for the reportAction which does have the action type as {!shouldHideAction && renderReportActionItem(hovered || isReportActionLinked, isWhisper, hasErrors)} Kapture.2023-10-20.at.18.01.30.mp4 |
RCA for double system message when a payer pays the money request via wallet flow: We have two IOU actions when a user pays a money request via wallet(one for create and one for pay). Create IOU action gets used for rendering the MoneyRequestAction from here: App/src/pages/home/report/ReportActionItem.js Line 319 in 69cf29e
The reimbursememntQueued action gets used to show the enable wallet button and the system message informing we are waiting for the payee to enable their wallet/bank account. The remaining IOU action(type:Pay) falls under else block here: App/src/pages/home/report/ReportActionItem.js Line 414 in 69cf29e
isWaitingBankAccount is set on the report.(Checkout the getReportPreview method).
Solution: |
Job added to Upwork: https://www.upwork.com/jobs/~01d5e47fb869ecebeb |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
📣 @situchan 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@b4s36t4 the root cause is correct but the solution is wrong. |
@techievivek should we fix double message issue as well here and ask contributors update proposal? |
Yes, please.
Good one. 👌 |
@situchan @techievivek Will update my proposal soon. |
@situchan updated proposal for the first issue (GBR). Working on the double system message fix. Will update soon. |
Updated the proposal to include the double system message as well. |
👋 checklist time! Bump, @situchan. |
Not overdue, gentle bump @situchan ^ |
@trjExpensify, @techievivek, @b4s36t4, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
No regression. This is new feature. I am not sure regression test is needed as it requires gold wallet which QA team doesn't have. |
Interesting. @kevinksullivan @joekaufmanexpensify are their no wallet regression tests in the app? |
Settled up with you both! Keeping open for a sec while we discuss await this. |
@trjExpensify isn't this also eligible for urgency bonus? We have a single pr for the both issues can you check please? |
I don't think we double up the urgency bonus for every issue a PR is linked to. It's a bonus for moving forward the PR with urgency, so I applied it on the payment for the other issue. 👍 |
I see a few in testrail. I think the original P2P implementation was before we had standardized on the current regression testing system in Testrail. I bet the few that have been added were part of the #gold-wallets room/project. |
Erm, I might be blind. Mind linking me to them? |
@trjExpensify, @techievivek, @b4s36t4, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I see some in the |
Hm, weird place for them. Also, it's creating a
|
Ah, interesting. Then, maybe there aren't really any for the NewDot P2P yet |
Asked here in the #gold-wallets channel. |
@trjExpensify, @techievivek, @b4s36t4, @situchan Huh... This is 4 days overdue. Who can take care of this? |
Okay, put that on the radar of the gold wallets team. Going to close this out now. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Coming from : https://expensify.slack.com/archives/C05RECHFBEW/p1697739357210919
And #29430 is the relevant PR that will likely need to be revisited.
Action Performed:
Expected Result:
There should be a system message prompting the user to enable their wallet, and there should be a GBR in the chat for that user, since they have an outstanding action to collect the funds.
Actual Result:
There is no GBR
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: