-
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
[$1000] [mweb-Android] click on back button of device navigates to payments page instead of setting page #20681
Comments
Triggered auto assignment to @johncschuster ( |
Bug0 Triage Checklist (Main S/O)
|
The previous page is payments page. Why should it go to settings page? |
I don't think that's correct, @c3024. After clicking 'X' on the Plaid popup, you should be back on the payments page. Clicking back should bring you to the previous page, which should be the settings page. I've updated the repro steps to make that a bit clearer. |
@johncschuster Eep! 4 days overdue now. Issues have feelings too... |
Job added to Upwork: https://www.upwork.com/jobs/~017cf84038380781c3 |
Current assignee @johncschuster is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak ( |
Calm down, Melvin. I just triaged the issue. |
yeah, but in this case, it's a close/cancel button. So clicking 'X' on the Plaid popup, I think we should be back on the payments page so user can select other payment options |
@hoangzinh I get where you're coming from, but I think the 'X' would simply close the modal, which should bring us back to the last thing we saw before the modal, right? Your suggestion is more like a redirect, isn't it? |
sorry @johncschuster I think I didn't all steps to reproduce this issue carefully. Originally I thought when we click "X" we would like to navigate back to Setting page. |
Looks like something related to As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our Feel free to drop a note in #expensify-open-source with any questions. |
@eVoloshchak can you take a look at the above proposal when you get a moment? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@johncschuster @eVoloshchak this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Looks like we're still waiting on proposals for this one. |
Thanks @srikarparsi! |
check up: https://expensify.slack.com/archives/CCQJP89RV/p1691000228916339?thread_ts=1689928793.556129&cid=CCQJP89RV. Said they'll have an update by the end of the week. |
Awesome. Thanks for the update! |
They said a fix should be in place but it doesn't seem to be. Sent a message following up: https://expensify.slack.com/archives/CCQJP89RV/p1691084404394809?thread_ts=1689928793.556129&cid=CCQJP89RV |
The fix has been deployed and it works. If there are no payments to be made, this issue should be good to close out @johncschuster |
Hey @johncschuster! Just wanted to bump this |
Sorry, John is OOO, couldn't find when he's back on the calendar but will reassign on Wednesday if he isn't back. |
Hey hey! I think my status in NewDot was incorrect – I'm not OOO. I'm catching up now! |
Hey @johncschuster! Just wanted to bump this for payment :) |
@johncschuster, @eVoloshchak, @srikarparsi Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Hey @johncschuster! Bump on the above. |
Derp! I'm sorry for missing this! Catching up now. |
Ok! It looks like this is good to close out. Closing! |
Payment is pending here |
Payment has been issued! (Thanks for the callout, @mananjadhav!) |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
settings
>payments
add payment method
buttonbank account
optionpayments
page)settings
page)Note on step 5: if you click the the back caret icon, the app will navigate back to the
settings
page as expected. To reproduce this behavior, you need to make sure you are clicking the physical back button on the device.Expected Result:
should navigate to settings page
Actual Result:
navigates to payments page
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.27-2
Reproducible in staging?: y
Reproducible in production?: y
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_20230608_000513_Chrome_1.mp4
az_recorder_20230613_103406.1.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686163312643879
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: