-
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-12-19] [$125] Web - RHP - Going back closes the RHP Instead of navigating to the confirm page #53253
Comments
Triggered auto assignment to @twisterdotcom ( |
Edited by proposal-police: This proposal was edited at 2024-11-28 15:59:30 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Web - RHP - Going back closes the RHP Instead of navigating to the confirm page What is the root cause of that problem?We are navigating back without the
What changes do you think we should make in order to solve the problem?We need to pass the backTo to the
What alternative solutions did you explore? (Optional)But if we want to navigate to the backTo only on BackButtonPressed here
and not onClose and onModalHide we can create a separate onBackPressed prop for ValidateCodeActionModal and pass the goBack with backTo passed as a callback and call it from only onBackButtonPress so that the onClose and onModalHide will call the normal backTo or dismissModalApp/src/components/ValidateCodeActionModal/index.tsx Lines 57 to 59 in 64eaf2f
|
@twisterdotcom Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Job added to Upwork: https://www.upwork.com/jobs/~021864112749864088782 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann ( |
Upwork job price has been updated to $125 |
@FitseTLT's proposal looks good to me 🎀 👀 🎀 C+ Reviewed |
Triggered auto assignment to @dangrous, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Yep that looks good to me! |
📣 @DylanDylann 🎉 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 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.74-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-12-19. 🎊 For reference, here are some details about the assignees on this issue:
|
@DylanDylann @twisterdotcom @DylanDylann 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: 9.0.68-0
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: #51630
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Going back should navigate us to the confirm page.
Actual Result:
Going back closes the RHP
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6679178_1732806280071.bandicam_2024-11-28_17-51-50-902.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: