-
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
Wallet - Confirm button is not shown on the currency selector page #55678
Comments
Triggered auto assignment to @yuwenmemon ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
🚨 Edited by proposal-police: This proposal was edited at 2025-01-24 02:04:56 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Confirm button is not shown What is the root cause of that problem?We do not show confirm button on selection list here What changes do you think we should make in order to solve the problem?If we just want to add Confirm button to the currency list in add bank account flow, Introduce In onConfirm={(e, item) => updateInput(item)} In order to do that, we need to update App/src/components/CurrencyPicker.tsx Line 33 in 034c4ca
The confirm button here simply just navigate back when no thing new was selected. What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?NA What alternative solutions did you explore? (Optional)Or we can modify the currency flow to work like |
@MonilBhavsar @shubham1206agra Seems like this is also related to #54798? |
@yuwenmemon This was decided to be as expected. There will be confirm button in currency selection page. You can close this issue. |
Nice, at least marking NAB for now, @yuwenmemon can close |
Well, it sounds like we need to update the regression steps at least. @MonilBhavsar, since this is your project, are you able to take care of that? |
I will, thanks! |
@shubham1206agra Do you mind linking me to thread about this? I know we had a lot of discussions about the feature in Slack, but I don't remember cutting the confirm button on this page. And all the design doc mockups show it/discuss it being there. I totally might be misremembering, but just want to make sure I am following so I can update the tests if we talked about cutting this. |
Current assignee @joekaufmanexpensify is eligible for the Bug assigner, not assigning anyone new. |
Got it, thanks! In the future, could you please tag me and @MonilBhavsar if we're contemplating changes to the design agreed on in the design doc? I don't think we were aware that we were removing this button. |
After doing some more research in the app, I think it's fine to leave this as is though, especially if it would be a lot of work to refactor this page to add the button. I'll update the regression test and then we can close this. |
Updated tests to clarify this. |
Closing as this is all set! |
Thank you Joe! |
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.89-2
Reproducible in staging?: Y
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #54798
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Component: User Settings
Action Performed:
Expected Result:
You see the Confirm button at the bottom
Actual Result:
Confirm button is not shown
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6722172_1737666570946.Screen_Recording_2025-01-24_at_12.00.48_at_night.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: