Skip to content

[Payment 2025-11-10] [$250] Report field - RHP shows Not here page while it closes after deleting the report field #71859

Closed

Description

@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.2.23-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1142/41237643/933087105?q=report+field&issue_type=jira
Email or phone of affected tester (no customers): ajsoinjaoijoajioj@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Reports
  3. Enable Report fields and upgrade the workspace
  4. Create any type of report field
  5. Go to workspace chat
  6. Click + > Create report
  7. Go back to workspace settings > Reports
  8. Delete the report field created in Step 4
  9. Go to workspace chat
  10. Open the report created in Step 6
  11. Click Report field
  12. Click 3-dot menu > Delete
  13. Delete the report field

Expected Result:

RHP will not show Not here page after deleting the report field

Actual Result:

RHP shows Not here page while it closes after deleting the report 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
Bug6964402_1759549710919.Screen_Recording_2025-10-04_at_11.44.45.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021975653582402707041
  • Upwork Job ID: 1975653582402707041
  • Last Price Increase: 2025-10-21
  • Automatic offers:
    • nkdengineer | Contributor | 109234871
Issue OwnerCurrent Issue Owner: @strepanier03

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 4, 2025
  2. melvin-bot commented on Oct 4, 2025

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

  3. nkdengineer commented on Oct 4, 2025

    @nkdengineer
    Contributor

    🚨 Edited by proposal-police: This proposal was edited at 2025-10-13 16:03:14 UTC.

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    RHP shows Not here page while it closes after deleting the report field

    What is the root cause of that problem?

    We have a race condition here

    const handleReportFieldDelete = () => {
    deleteReportField(report.reportID, reportField);
    setIsDeleteModalVisible(false);
    goBack();
    };

    • The optimistic update of deleteReportField makes reportField become null
    • Navigation goBack() not completing in time
    • Component re-rendering with reportField = null → triggering the condition to show "not found"

    What changes do you think we should make in order to solve the problem?

    We should wrap in deleteReportField in the delay mechanism to ensure navigation completes before the optimistic update occurs like the way we did with delete taxes here

        const handleReportFieldDelete = () => {
            setIsDeleteModalVisible(false);
            goBack();
            // Delay the deletion to avoid a race condition with navigation
            setTimeout(() => {
                deleteReportField(report.reportID, reportField);
             }, CONST.ANIMATED_TRANSITION); // 300ms
        };
    

    Note 1: Because InteractionManager.runAfterInteractions is about to be deprecated, we can use another delay mechanism as a replacement — for example, setTimeout or requestIdleCallback as React suggests here.
    Note 2: we can check other pages that has the same error and fix in this issue

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    None

    What alternative solutions did you explore? (Optional)

    Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 7, 2025
  5. changed the title [-]Report field - RHP shows Not here page while it closes after deleting the report field[/-] [+][$250] Report field - RHP shows Not here page while it closes after deleting the report field[/+] on Oct 7, 2025
  6. melvin-bot commented on Oct 7, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 7, 2025
  8. melvin-bot commented on Oct 7, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @hungvu193 (External)

  9. hungvu193 commented on Oct 9, 2025

    @hungvu193
    Contributor

    We should wrap in deleteReportField in the InteractionManager.runAfterInteractions to ensure navigation completes before the optimistic update occurs like the way we did with delete taxes here

    InteractionManager will be deprecated as soon as we upgrade the react native version to the latest (0.82.0). I don't think we should do it here.

    FYI: https://reactnative.dev/docs/interactionmanager

  10. 45 remaining items

  11. nkdengineer commented on Nov 21, 2025

    @nkdengineer
    Contributor

    @strepanier03 @garrettmknight I get paid via NewDot now.

  12. melvin-bot commented on Nov 28, 2025

    @melvin-bot

    @nkdengineer Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  13. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    @nkdengineer Huh... This is 4 days overdue. Who can take care of this?

  14. melvin-bot commented on Dec 2, 2025

    @melvin-bot

    @strepanier03 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  15. melvin-bot commented on Dec 4, 2025

    @melvin-bot

    @strepanier03 Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

  16. dangrous commented on Dec 11, 2025

    @dangrous
    Contributor

    Where are we on this one? Is payment all set or do we still need to do something before closing? Thanks!

  17. melvin-bot commented on Dec 11, 2025

    @melvin-bot

    This issue has not been updated in over 14 days. @dangrous, @pecanoro, @strepanier03, @hungvu193, @nkdengineer eroding to Weekly issue.

  18. added and removed on Dec 17, 2025
  19. CortneyOfstad commented on Dec 22, 2025

    @CortneyOfstad
    Contributor

    Coming from this request, I reviewed and both are paid via Newdot. Confirmed the proposal in Upwork expired, so all set 👍

    Payment Summary

    @hungvu193 — to be paid $250 via NewDot
    @nkdengineer — to be paid $250 via NewDot

  20. twisterdotcom commented on Mar 11, 2026

    @twisterdotcom
    Contributor

    @nkdengineer has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Zapier Logs Run ID: 00040eee-21b1-ac78-98d9-27de04b09094
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions