-
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
[HOLD for payment 2024-04-15] [$750] mWeb - Click on back button from country picker page redirects to wrong page #23725
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @MariaHCD ( |
I don't necessarily think this should block the deploy. Looks like this PR introduced the updates for the country picker: #21049 |
@MariaHCD This is not a blocker. This is same for Year picker and similar parts of the form. The Year page or in this case the State or Country picker are not its own route/ page in the stack hence when you click back it takes you to the personal details. I think its something we might have to look at as a general solution as I think we would like this fixed for consistency, but its not a blocker. I will demote this and add it to the navigation follow ups tracking project. |
Triggered auto assignment to @greg-schroeder ( |
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
Current assignee @greg-schroeder is eligible for the NewFeature assigner, not assigning anyone new. |
Current assignee @shawnborton is eligible for the NewFeature assigner, not assigning anyone new. |
Perfect, thanks @mountiny! Not familiar with the |
@MariaHCD I will post this in SWM channel to let the guys know an dI think they will take it posting NewFeature as I think its more true than bug |
This issue has not been updated in over 15 days. @parasharrajat, @greg-schroeder, @WoLewicki, @mountiny, @ygshbht eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Merged, awaiting deploy to staging -> prod |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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-04-15. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Okay this issue is crusty AF, gonna take some time to review who did what along the way here |
@gadhiyamanan reported this issue 2023-07-26 - $50- Reporter |
I'm going to create manual offers for this one as the original Upwork issue is long since closed, stand by Payment issue: #40223 Offers sent to reporter and contributor - Rajat you can make a manual request in ND for $1500, then can you complete the checklist? Thanks! |
Regression Test StepsVerify for places where you have to select an American State from a list: For Personal Address:
For debit card page:
For ReimbusementAccountPage
Do you agree 👍 or 👎 ? |
I think we should add a test for this but one should be enough. I would say lets use the @greg-schroeder would you be able to add this one? thanks! |
This comment was marked as off-topic.
This comment was marked as off-topic.
Added, closing! |
Payment requested as per #23725 (comment) |
Asked for confirmation on the intended amount in New Expensify. |
@greg-schroeder would you mind double confirming that the automated summary is wrong, and that your summary here is right? |
Hey @JmillsExpensify - yes, I was going off of pricing that Vit laid out here: |
Thanks! $1,500 approved for @parasharrajat |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Problem
The country picker in Personal Details > Home Address is made of a component which is controlled in state and it does not have its own route. This was made to simplify reusing the component in various places in the app as its easier to just plug it into some page and let its open/ closed state be controlled from within the parent component as well as take the selected value and save it in the parent form.
This however leads to unexpected navigation behaviour with the back button in browser or in android, because the component is not its own page hence its not a screen in the browser history either.
Now that we got a good solution pattern in place with the
IOUCurrencySelection
component reused for 1. creating money request, 2. Confirming creation of money request and 3. Editing money request amount, all done using the same component and having its own path which allows for correct and predictable navigation.Solution
Lets build the Country picker page as we did
IOUCurrencySelection
using its own route acceptinggoBack
as url param, and making sure the AddressPage will consume the country picked from the?country
url param same as we do with?currency
in the other case.Action Performed:
Expected Result:
Should navigates to Home address screen
Actual Result:
Navigates to Personal details screen
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.45-8
Reproducible in staging?: y
Reproducible in production?: new feature
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
Notes/Photos/Videos: Any additional supporting documentation
Screen_Recording_20230726_193945_Chrome.mp4
Screen_Recording_20230727_071059_Chrome.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690380615025549
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: