Report fields - The report field after deleted offline is still clickable

[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!

---

Found when validating #44493
Version Number: 9.0.5-3
Reproducible in staging?: y
Reproducible in production?: no, this is new feature
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: Applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Report fields (Enable on More features if not yet).
3. Add any type of report field.
4. Go offline.
5. Click on the report field.
6. Click Delete.
7. Delete the field.
8. Click on the deleted report field.

Expected Result:

The report field after deleted offline should no longer be clickable.

Actual Result:

The report field after deleted offline is still clickable.

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

Bug6535909_1720446467435.20240708_214426.mp4

View all open jobs on GitHub

[melvin-bot]

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

[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]

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

[m-natarajan]

@strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[m-natarajan]

We think that this bug might be related to #wave-collect - Release 1

[mountiny]

Taking to over as I work on the project, this is still behind beta so not a blocker

@waterim @rezkiy37 who can take this?

[waterim]

Hello, Im Artem from Callstack and this one will addressed here

[melvin-bot]

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

[rushatgabhane]

PR reviewed and merged