User is able to request an IOU from Concierge

[kavimuru]

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. Sign up with a new account
2. Click on 'Request money' link
3. Enter amount & Click on 'Next' button
4. Select 'Concierge' from the contacts section
5. Click on 'Request' button

Expected Result:

Concierge shouldn't be listed on the contacts section of an IOU flow

Actual Result:

Concierge is listed on the contacts section of an IOU flow

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?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.29-0
Reproducible in staging?: y
Reproducible in production?: n
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

Screencast.from.2023-06-18.18-01-12.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687100910635549

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @tjferriss (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[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.

[melvin-bot]

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

[Natnael-Guchima]

On the video is a list of places where Concierge starts to appear after the latest staging release.

Screencast.from.2023-06-18.21-31-32.webm

[Pujan92]

@Natnael-Guchima Is it only for new accounts bcoz I am not able to reproduce it?

[Natnael-Guchima]

@Pujan92 I think it is only reproducible for new accounts with no prior chat history It should be reproducible on existing accounts.

[Pujan92]

Ok, somehow not able to reproduce in dev.

[neil-marcellini]

I'm only able to reproduce with a brand new account. I'll add that to the steps in the description.

[tjferriss]

I'm able to reproduce the issue using a brand new account.

[luacmartins]

More context here. This Auth PR seems to fix the issue. I'll remove the blocker label and put this issue on hold for the Auth deploy. Once we deploy, we should confirm this is fixed on staging.

[tjferriss]

It looks like the Auth PR has been deployed. Can we take this off hold?

[neil-marcellini]

Yep! @tjferriss would you please see if this is fixed on staging?

[neil-marcellini]

Gentle bump @tjferriss

[Natnael-Guchima]

This seems to be fixed on the latest release.

[neil-marcellini]

Great, thanks you, closing this. No reporting bonus is needed since applause reported it.

[Natnael-Guchima]

@neil-marcellini I am the one who reported this issue. You can find my name on the 'issue reported by' section.

[neil-marcellini]

I responded on Slack here.