Web – Request Money - "Report Not Found" Error expensify.com sign-in page opens by the Email link

[izarutskaya]

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. Click the green + icon and select request money

2. Enter an amount and click next

3. Enter the email address of a user that doesn't have an existing account and request $x to confirm and send the request.

4. Go to the email inbox of that user you just invited and make sure the email is received - it will look like this
   

5. Click the "Expensify" hyperlink in the email

Expected Result:

Navigated to the New Expensify sign-in page and not the expensify.com sign-in page.

Actual Result:

Navigated to the expensify.com sign-in page with The Error message "Report not Found"

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Version Number: 1.3.65-0

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

Bug6190827_OldDot_2.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation: @

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~013568bf585c519a67
• Upwork Job ID: 1699857983227707392
• Last Price Increase: 2023-09-07

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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

[Christinadobrzyn]

I can reproduce this - I can't find any other reports of this.
I think this needs to be internal but not quite sure...

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~013568bf585c519a67

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @rushatgabhane (Internal)

[melvin-bot]

@rushatgabhane, @Christinadobrzyn Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@rushatgabhane, @Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[Christinadobrzyn]

Hey @rushatgabhane can you confirm if this should be internal? I can add an engineering label if yes. Thanks!

[rushatgabhane]

@Christinadobrzyn yes, this is internal.

[melvin-bot]

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

[Christinadobrzyn]

Hi @chiragsalian let me know if you have the bandwidth to take this job on and an update on a PR. thanks!

[chiragsalian]

Hi Christina, im swamped. Could you find another engineer to tackle this or should i unassign and post in engg chat instead?
Also is this a daily. I'm wondering if it could be demoted to weekly instead.

[melvin-bot]

@marcochavezf @Christinadobrzyn this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[Christinadobrzyn]

I don't think WAQ applies here because this is an internal issue and not customer-facing. But going to move this back to weekly. I wonder if this should be monthly even?

[melvin-bot]

@marcochavezf @Christinadobrzyn this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

[Christinadobrzyn]

I'm not sure what to do with this issue - maybe I should reach out in BZ room and see if someone else can take it? Seems like moving to monthly doesn't stop the WAQ messaging.

Reached out to @marcochavezf to see if he has an idea

[melvin-bot]

@marcochavezf, @Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[marcochavezf]

I will work on this one today

[marcochavezf]

We're probably not setting the param isChat for this condition when we call the API command RequestMoney. For some reason, my bwm is stuck to debug the issue. I will continue later

[Christinadobrzyn]

working on it Melvin!

[marcochavezf]

Still wrapping up some priorities for wave7, no update atm

[marcochavezf]

No update, tackling one issue by one

[marcochavezf]

No update, focused on TU launch

[marcochavezf]

No update

[Christinadobrzyn]

Should I move this to weekly @marcochavezf?

[marcochavezf]

Thanks for the suggestion @Christinadobrzyn, I already have a fix for it I will create a PR tomorrow, so I will leave it as daily atm since it can be experienced by real customers with the latest wave launches.

[marcochavezf]

Oh noticed this is no longer an issue:

Dev:

Staging (we're not sending emails from staging, but the report can be opened if we add the staging subdomain to the url):

@izarutskaya could you verify from your end too?

[marcochavezf]

Closing it out because it's already fixed