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

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

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

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

Issue not reproduce when we disabled Use Staging Server

Confirmed that this is not reproducible with Use Staging Server disabled. This should be a web blocker.

It doesn"t look like there"s anything wrong with DeleteMoneyRequestOnSearch on staging. The responses look similar on staging and prod.

Instead I think there"s something broken with creating the expense in RequestMoney. If I create the expense with prod and delete it with staging, it works fine. Only creating the expense on staging causes the issue.

I"m more confused now.

• I looked at the diff between staging and prod for RequestMoney and DeleteMoneyRequestOnSearch responses and didn"t notice any important differences
• In DeleteMoneyRequestOnSearch response, there"s an update to clear the report and transaction from the snapshot but from logs and the values in IndexedDB, this is NOT being merged:

So I think the root of this problem lies more in the way we"re processing Onyx updates. Which means this might actually need to be an App blocker.

I don"t see any relevant App changes in the current deploy 😕. I"ll try reproducing this in dev and finding the root cause.

Unfortunately, I"m having trouble reproducing in dev. And now even on staging I"m having trouble reproducing 🙃.

I think there"s probably a subtle bug with the way Onyx updates are handled here, but I don"t think any of the changes in the current deploy are causing it. I"m going to demote this and revisit next week to see if it"s still reproducible.

@JmillsExpensify, @arosiclair Whoops! This issue is 2 days overdue. Let"s get this updated quick!

No updates. Waiting until the next deploy.

Still not reproducible in v9.0.78-2:

Closing this out