Skip to content
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

Payments - Unable to change PayPal account in Setting, green button always enabled. #3609

Closed
isagoico opened this issue Jun 16, 2021 · 14 comments
Assignees
Labels
Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@isagoico
Copy link

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Launch the app
  2. Log in with any account
  3. Click on aviator
  4. Go to Settings- Payments
  5. Change your PayPal account

Expected Result:

Able to change PayPal account

Actual Result:

Unable to change PayPal account in Setting, green button always enabled.

Workaround:

User has to change paypal account in e.com

Platform:

Where is this issue occurring?

Web ✔️
iOS ✔️
Android ✔️
Desktop App ✔️
Mobile Web ✔️

Version Number: 1.0.69-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

Bug5115632_Screen_Recording_20210616-073859_Expensifycash.mp4

image

Expensify/Expensify Issue URL:

View all open jobs on Upwork

@MelvinBot
Copy link

Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@rushatgabhane
Copy link
Member

rushatgabhane commented Jun 16, 2021

Platform : Windows, Chrome.
I followed the steps and added new PayPal username.

The green button got disabled.
And it stayed disabled, even after I came back to it.

I'm unable to change PayPal username though.

image

@rushatgabhane
Copy link
Member

rushatgabhane commented Jun 16, 2021

Proposal

In PaymentPage.js
TextInput has a prop editable which will be made true always.

This is what I think the expected behavior of button should be.

  • Disabled on empty username.
  • Enabled after typing a username.
  • Disabled after successfully adding a username.
  • Button is enabled again if I change the username.

Modify the isDisabled prop of Button in PaymentPage.js to get this behaviour.

Thoughts on if this is what you think expected behaviour of Button should be?

@marcaaron
Copy link
Contributor

Yes there is definitely some kind of regression here. If I had to guess I'd say it's related to the changes here -> https://github.com/Expensify/Expensify.cash/pull/3391/files

@jasperhuangg can you look into this for us?

@marcaaron marcaaron added the External Added to denote the issue can be worked on by a contributor label Jun 16, 2021
@MelvinBot
Copy link

Triggered auto assignment to @trjExpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@marcaaron
Copy link
Contributor

@trjExpensify let's hold to see what @jasperhuangg says before creating an External issue for this ?

@trjExpensify
Copy link
Contributor

Yep! 👍

@isagoico
Copy link
Author

Issue reproducible today during KI retests.

@trjExpensify
Copy link
Contributor

👋 @jasperhuangg any update on this? #3609 (comment)

@isagoico
Copy link
Author

Issue reproducible during KI retests.

@jasperhuangg
Copy link
Contributor

Hey guys! So sorry, I've completely been missing these notifications for whatever reason. I'll look into this first thing tomorrow.

@isagoico
Copy link
Author

isagoico commented Jul 5, 2021

Issue reproducible during KI retests.

@trjExpensify
Copy link
Contributor

PR is up, just waiting on being deployed to staging.

@isagoico
Copy link
Author

isagoico commented Jul 12, 2021

Issue not reproducible during KI retests. Looks like this one was fixed, closing it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests

6 participants