Skip to content

[HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] Report fields - "title" report field shows up and app crashes when clicking on checkbox. #44797

Description

@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: 9.0.4.0
Reproducible in staging?: y
Reproducible in production?: no, 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 Account settings.
  3. Create a new workspace.
  4. Quickly go to More features and enable Report fields.
  5. Note that "title" report field appears. (might need to repeat Step 3 to 5 a few times)
  6. Click on the "title" checkbox.

Expected Result:

"title" report field will not show up and app will not crash when clicking on the checkbox.

Actual Result:

"Title" report field shows up and app crashes when clicking on the checkbox.

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

Bug6532499_1720042271423!crash.txt

Bug6532499_1720042271417.crash.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @slafortune

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 4, 2024
  2. melvin-bot commented on Jul 4, 2024

    @melvin-bot

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

  3. melvin-bot commented on Jul 4, 2024

    @melvin-bot

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

  4. github-actions commented on Jul 4, 2024

    @github-actions
    Contributor

    👋 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.
  5. m-natarajan commented on Jul 4, 2024

    @m-natarajan
    Author

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

  6. m-natarajan commented on Jul 4, 2024

    @m-natarajan
    Author

    We think that this bug might be related to #vip-vsb

  7. nyomanjyotisa commented on Jul 4, 2024

    @nyomanjyotisa
    Member

    Proposal

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

    title" report field shows up and app crashes when clicking on checkbox.

    What is the root cause of that problem?

    The CreateWorkspace contains one fieldList onyxData
    Screenshot 2024-07-04 at 17 05 11

    There seems already a filter for it, but it not working properly

    const filteredPolicyFieldList = useMemo(() => {
    if (!policy?.fieldList) {
    return {};
    }
    return Object.fromEntries(Object.entries(policy.fieldList).filter(([key]) => key !== 'text_title'));
    }, [policy]);

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

    Update the filter to filter by value.fieldID instead of key

        const filteredPolicyFieldList = useMemo(() => {
            if (!policy?.fieldList) {
                return {};
            }
            return Object.fromEntries(Object.entries(policy.fieldList).filter(([_, value]) => value.fieldID !== 'text_title'));
        }, [policy]);
    

    What alternative solutions did you explore? (Optional)

  8. 24 remaining items

  9. melvin-bot commented on Jul 10, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  10. melvin-bot commented on Jul 10, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.5-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-07-17. 🎊

    For reference, here are some details about the assignees on this issue:

  11. melvin-bot commented on Jul 10, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@rushatgabhane / @shubham1206agra] The PR that introduced the bug has been identified. Link to the PR:
    • [@rushatgabhane / @shubham1206agra] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@rushatgabhane / @shubham1206agra] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@rushatgabhane / @shubham1206agra] Determine if we should create a regression test for this bug.
    • [@rushatgabhane / @shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@slafortune] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  12. changed the title [-][HOLD for payment 2024-07-17] Report fields - "title" report field shows up and app crashes when clicking on checkbox.[/-] [+][HOLD for payment 2024-07-22] [HOLD for payment 2024-07-17] Report fields - "title" report field shows up and app crashes when clicking on checkbox.[/+] on Jul 15, 2024
  13. melvin-bot commented on Jul 15, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.6-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2024-07-22. 🎊

    For reference, here are some details about the assignees on this issue:

  14. melvin-bot commented on Jul 15, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@rushatgabhane / @shubham1206agra] The PR that introduced the bug has been identified. Link to the PR:
    • [@rushatgabhane / @shubham1206agra] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
    • [@rushatgabhane / @shubham1206agra] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
    • [@rushatgabhane / @shubham1206agra] Determine if we should create a regression test for this bug.
    • [@rushatgabhane / @shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [@slafortune] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  15. slafortune commented on Jul 18, 2024

    @slafortune
    Contributor

    @rushatgabhane @shubham1206agra can you please complete the checklist?

  16. mountiny commented on Jul 19, 2024

    @mountiny
    Contributor

    @slafortune this is a new feature and we are handling all these cases as part of the report fields configuration project so I think we can close this issue now, payments are done per project

  17. moved this from Release 2: Summer 2024 (Aug) to Done in #expensify-bugson Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions