Dev : Single transaction expense report is wrong after creating the first transaction, it gets fixed if you open the expense report again

[m-natarajan]

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:
Reproducible in staging?:
Reproducible in production?:
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
Expensify/Expensify Issue URL:
Issue reported by: @aldo-expensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Create an expense report in your policyExpenseChat
2. Go to the expense report
3. Create a transaction

Expected Result:

The details of the transaction should be visible within the expense report and there shouldn't be a preview reportAction

Actual Result:

The expense report with a single transaction looks like an expense report with multiple transactions (report action preview and no transaction details)

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

View all open jobs on GitHub

[melvin-bot]

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

[aldo-expensify]

The bug may be coming from here: https://expensify.slack.com/archives/C049HHMV9SM/p1754942356969809?thread_ts=1754941038.145369&cid=C049HHMV9SM

Not sure yet why the optimistic "IOU" reportAction is missing childReportID

[aldo-expensify]

This may be coming from this PR: #68009

cc @VickyStash

[aldo-expensify]

Yep, if I replace const shouldGenerateTransactionThreadReport = !isBetaEnabled(CONST.BETAS.NO_OPTIMISTIC_TRANSACTION_THREADS); by const shouldGenerateTransactionThreadReport = true; everywhere, the bug is gone

[VickyStash]

Yep, if I replace const shouldGenerateTransactionThreadReport = !isBetaEnabled(CONST.BETAS.NO_OPTIMISTIC_TRANSACTION_THREADS); by const shouldGenerateTransactionThreadReport = true; everywhere, the bug is gone

I think this is expected, please check the PR description:

❗ It's expected that the functionality related to the expense without transaction thread won't work as expected/be limited. It will be implemented incrementally in the separate issues. Please, TURN OFF noOptimisticTransactionThreads beta if you need to test the expenses-related functionality.

The described issue should be fixed with this issue: Update one transaction thread expense in the chat to work as expected if no optimistic thread report was created

[VictoriaExpensify]

I thinkg @VickyStash is right and that this is expected. @aldo-expensify do you agree?

[aldo-expensify]

Yes! I missed that section of the description when I was investigating yesterday. Thank you @VickyStash.

I'll close this, sorry for the confusion!