Payments - ''Add pay method'' button flashes when tapped on it

[kbecciv]

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. Tap on Avatar - Setting - Payments
4. Tap ''Add pay method'' button

Expected Result:

''Add pay method'' button is not flash when tapped on it

Actual Result:

''Add pay method'' button flashes when tapped on it

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Android
• Desktop App
• Mobile Web

Version Number: 1.1.74.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

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

Notes/Photos/Videos: Any additional supporting documentation

ios.0806.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[Luke9389]

It's pretty hard to see exactly what's happening here. The transparent layer could be flashing out, or the button style could be turning dark green again.

Definitely seems like it can go External.

[melvin-bot]

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

[Luke9389]

Actually, @JmillsExpensify, do you think this issue is well-formed enough to export? We might want to clear up the expectations for the deliverables here before we start spending time on proposals.

[Luke9389]

Getting @JmillsExpensify's take before moving forward with this.

[JmillsExpensify]

I think we should probably put this one hold. We're about to redo this entire page for N7. Another alternative is to close it for now given that we don't have a use case that supports the Wallet page in the production app.

[Luke9389]

OK between those two I think closing is the better action to take. We'll perform tests and create follow up issues after the refactor, which will be made more simple if there isn't confusion between old and new problems.

[JmillsExpensify]

Awesome, yes this sounds great!