Android - Expense is auto categorized to previously select categorization

[lanitochka17]

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.1.65-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: https://expensify.testrail.io/index.php?/tests/view/6225708
Issue reported by: Applause - Internal Team

Action Performed:

Pre-condition: User has workspace created with categories enabled
Steps

1. Log in to the hybrid app
2. Navigate to the workspace conversation
3. Create an expense with only a merchant and amount field filled (no categories selected)
4. Open the expense details for the expense created in step 3
5. As the concierge suggests a list of categories to select, select from the suggested list by selecting or writing the category name
6. Navigate to workspace conversation
7. Create another expense with a different merchant and amount (no categories selected) ( 2 times)
8. Navigate to expense details for expense created in step 7

Expected Result:

Concierge message is displayed with a list of categories to select from

Actual Result:

Category selected from the previous concierge list is displayed in the new category field

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6858360_1749754754637.video_2025-06-12_21-57-22.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[BlameGPT]

Possible culprit PRs for this issue

• Fix - Update empty state for tag and category #62670: This PR updates the empty state for tags and categories, directly involving category UI components and flows related to categories, which aligns with the issue about category selection and display.
• Expense - In merged archived workspace, tapping add expense via report shows hmm not here page #63541: This PR involves expense creation flows in workspaces and report-related UI components, which partially overlaps with the issue's workspace expense creation and category selection steps.
• Fix - Incorrect policy audit log messages for adding/updating the payroll code or GL code category fields #62331: This PR modifies category-related workspace settings and UI messages, which could impact category handling and display in workspace expenses.

[rushatgabhane]

this looks like backend to me

[Julesssss]

Agree with this not seeming to be a frontend app blocker, especially given the diff on this checklist. It might not be reproducable on prod due to the non-deterministic behaviour.

I believe we expect concierge to auto-select a category when it has high confidence. One thing is confusing me though, we seem to be changing the category AFTER it was created and leaving a comment -- which doesn't quite match the DD. I just want to check this is expected.

[Julesssss]

Confirmed that we expect the concierge comment to be left on any expense update. I'm going to close this issue as expected behaviour.