Xero -"manually exported" message only appears after revisting export and it is missing "Xero"

[izarutskaya]

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

---

Version Number: 9.0.8-1
Reproducible in staging?: Y
Reproducible in production?: N
Found when executing PR : #44170
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition:

• Admin and employee are in the same workspace.
• Workspace is connected to Xero.

1. Go to staging.new.expensify.com
2. [Employee] Submit an expense in the workspace chat.
3. [Admin] Go to workspace chat with employee.
4. [Admin] Click on the expense preview.
5. [Admin] Pay elsewhere the report.
6. [Admin] Click "Mark manually as entered" button.

Expected Result:

• "manually exported" system message will show up in report without revisiting the report.
• "manually exported" system message will be complete.

Actual Result:

• "manually exported" system message only shows up in report after revisiting the report.
• "marked this report as manually exported to " system message is missing "Xero".

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6544833_1721204151988.20240717_161123.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @anmurali (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @MariaHCD (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

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

[izarutskaya]

We think this issue might be related to the #collect project.

[izarutskaya]

Production

[MariaHCD]

Hmm, looks like we noticed that the name of the platform is missing before we merged the PR: #44170 (comment)

But we can potentially ignore this for now? #44170 (comment)

cc: @arosiclair @francoisl

[kosmydel]

I think we can ignore it for now. It was noticed here, and we have decided that the issue is the backend side here.

[MariaHCD]

Cool, this doesn't need to block the deploy, then.

@arosiclair @francoisl Do we have an issue to track the BE fix?

[arosiclair]

@arosiclair @francoisl Do we have an issue to track the BE fix?

I don't think so. Let's use this one to track it. I'll take over cc @lakchote as well

[arosiclair]

Alright this is happening because I forgot to add EXPORTINTEGRATION to our list of actions we queue onyx updates for here. I'll post a PR to fix that

[arosiclair]

PR hit prod last week. This is all set.