Android/IOS - Undefined showed instead of phone number after Pay by Venmo

[kbecciv]

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:

1. Lunch the app
2. Login with phone number account (Account A)
3. Request money from another phone number account (Account B)
4. Log in with Account B and tap on Pay button.
5. Select Pay with Venmo

Expected Result:

User should be redirected to correct Venmo account

Actual Result:

User redirected to Venmo app with placeholder Undefined account

Workaround:

Unknown

Platform:

Where is this issue occurring?

• iOS
• Android

Version Number: 1.1.24.0

Reproducible in staging?: Yes

Reproducible in production?: No

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5391124_Screen_Recording_20211229-191708_Venmo.mp4

Expensify/Expensify Issue URL:

Issue reported by:

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

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

[mananjadhav]

@nickmurray47 I was fixing the Paypal undefined issue and I've added a fix for the Venmo as well (the phone number wasn't passed similar to Paypal address).

[nickmurray47]

Yup, looks like that would solve the issue!

[parasharrajat]

Great seems like the same solution fixes both.

[mvtglobally]

@mananjadhav @nickmurray47 Are we good to re-test?

[nickmurray47]

I believe so, we applied the CP label so this should have gone directly to staging.

[mvtglobally]

Issue is fixed. Should I close it?

[nickmurray47]

I'll close!

[marcaaron]

I don't understand why this issue was not triaged, no Upwork created, and had a PR approved and merged. Seems like the process was not followed at all. Can someone explain why?

[parasharrajat]

Actually, this issue was reported after a similar issue was created. Manan already created the PR for #6947 which indirectly solves thus there is no job was created for this and we decided to close this.

On the other hand, the process was not followed for #6947. You can raise the same flag there.