-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-01-02] [HOLD for payment 2023-12-29] [$500] Contact method - Delete contact method confirmation pop-up appears after slight delay #33410
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 @NikkiWines ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Delete contact method confirmation pop-up appears after slight delay App/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js Lines 222 to 227 in 2f7c2b2
What is the root cause of that problem?It is caused by this pr to display modal after keyboard is dismissed What changes do you think we should make in order to solve the problem?We should do that only for touch screen App/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js Lines 222 to 227 in 2f7c2b2
change it to
What alternative solutions did you explore? (Optional) |
Hm... Is this a bug? We decided to run it after all interactions. |
This seems to only occur when the contact method is unvalidated, which makes sense given @allroundexperts's and @FitseTLT's comments above. I do think it comes across a bit buggy and we should fix it. Especially if we're applying logic that only impacts touchscreen devices to all platforms |
Anyway, @FitseTLT your solution looks good to me! Adding the relevant labels and assigning you 👍 |
Triggered auto assignment to @isabelastisser ( |
This comment was marked as outdated.
This comment was marked as outdated.
Job added to Upwork: https://www.upwork.com/jobs/~016b88b71e8f06ec60 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra ( |
📣 @shubham1206agra 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @FitseTLT 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@FitseTLT can you raise a PR quickly? |
K 👍 |
I think this should be handled as regression. The correct flow would be:
cc: @mallenexpensify (as we were discussing this process recently) |
@situchan above flow only applies only when the original author raised the PR without another proposal getting selected, and uses the solution from the proposal here |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.15-5 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 2023-12-29. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.16-5 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-01-02. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
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:
|
Issue is ready for payment but no BZ is assigned. @puneetlath you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Hm, @isabelastisser is already assigned. Not sure why it added me, but going to remove myself. |
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:
|
Hey @shubham1206agra, please accept the offer in Upwork and I will process the payment. Thanks! |
@isabelastisser Accepted |
The payment was made in Upwork. All set! |
@isabelastisser can you please post the amounts that were paid, to whom and their roles? I have this set at a TextExpander that I fill out each time.
|
Contributor: @FitseTLT paid $500 via Upwork |
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: 1.4.15-4
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:
Issue found when executing PR #32901
Action Performed:
Expected Result:
Delete confirmation pop-up appears without delay
Actual Result:
Delete confirmation pop-up appears after slight delay.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6322617_1703162575019.bandicam_2023-12-21_20-18-49-816.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @isabelastisserThe text was updated successfully, but these errors were encountered: