-
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
[$500] [HOLD for payment 2024-02-19] [HOLD for payment 2024-02-15] Request Money - The close button linked to "Request money. Get $250" is not functioning #36032
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @puneetlath ( |
We think that this bug might be related #vip-split-p2p-chat-groups |
Looks like a regression from But just in case, a proposition ProposalPlease re-state the problem that we are trying to solve in this issue.Request Money - The close button linked to "Request money. Get $250" is not functioning What is the root cause of that problem?The main problem with this issue is that we use static value for What changes do you think we should make in order to solve the problem?To fix this issue we can pass referralContentType instead of CONST.REFERRAL_PROGRAM.CONTENT_TYPES.REFER_FRIEND What alternative solutions did you explore? (Optional)NA |
ProposalPlease re-state the problem that we are trying to solve in this issue.Request Money - The close button linked to "Request money. Get $250" is not functioning What is the root cause of that problem?App/src/components/ReferralProgramCTA.tsx Lines 35 to 37 in 880e187
type is hardcoded here What changes do you think we should make in order to solve the problem?It should be (Optional) As a cleanup, remove all Edit: @ZhenjaHorbach edited comment with formal proposal following template after my proposal so I am the first. |
@cristipaval I feel like you would have the most context on this one. Do these proposals sound good? |
looking now |
Actually, you just took my explanation of this issue and made a proposition on it Therefore, just in case, I also made a proposal based on my comment which was long before your proposal ![]() |
@ZhenjaHorbach I just assigned you to fix the issue. You quickly found the root cause and it looks good to me. Please open a PR asap given that this is a deploy blocker. |
@puneetlath I took this one over because it's a regression from the PR that I was in charge of. |
No problem |
I agree that the one who first found the root cause and solution should be assigned, regardless of formal proposal or not. |
Ok thanks @cristipaval |
will post a patch very soon |
@lukemorawski This has been fixed already in this PR |
@cristipaval cool, thanks! |
Removing the blocker as this is from yesterday and this has been fixed already. |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.39-8 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-02-19. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@s77rt could you handle the BZ checklist so we can prep to issue payment this week? |
Regression Test Proposal
|
BZ checklist complete, and all set to issue payment! |
Job added to Upwork: https://www.upwork.com/jobs/~0140216d69adafd36d |
Current assignee @s77rt is eligible for the External assigner, not assigning anyone new. |
We need to make the following payments:
|
@s77rt offer sent for $500! |
@ZhenjaHorbach offer sent for $500! |
@joekaufmanexpensify Accepted! Thanks! |
@ZhenjaHorbach $500 sent and contract ended! |
@s77rt $500 sent and contract ended! |
Upwork job closed. |
All set. Thanks everyone! |
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: v1.4.38-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
1, Tap on the FAB
2. Select "Request money" manually.
3. Add the desired amount.
4. Observe that the Close button at the bottom of the modal linked with "Request money, $250" is not working.
Expected Result:
The Close button should close the associated statement
Actual Result:
The Close button linked to "Request money. Get $250" is not functioning
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6370418_1707315345782.Screen_Recording_2024-02-07_at_5.44.14_AM.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: