Skip to content

Desktop - App is crashing when select Priority mode  #7811

Closed

Description

@mvtglobally

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Open app
  2. Add few drafts to the different treads
  3. Navigate to Settings > Preferences > Choose Focus mode

Expected Result:

App should not crash

Actual Result:

App is crashing.
Issue is not repro after user switches mode few times back and forth, but its always repro on first change after opening app from background

Workaround:

unknown

Platform:

Where is this issue occurring?

  • Desktop App

Version Number: 1.1.39-1
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Recording.393.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Feb 18, 2022
  2. MelvinBot commented on Feb 18, 2022

    @MelvinBot
    Contributor

    Triggered auto assignment to @strepanier03 (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

  3. removed
    AutoAssignerTriageAuto assign issues for triage to an available triage team member
    on Feb 18, 2022
  4. OSBotify commented on Feb 18, 2022

    @OSBotify
    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. MelvinBot commented on Feb 18, 2022

    @MelvinBot
    Contributor

    Triggered auto assignment to @marcaaron (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  6. marcaaron commented on Feb 18, 2022

    @marcaaron
    Contributor

    Issue is not repro after user switches mode few times back and forth, but its always repro on first change after opening app from background

    So it is not reproducible with these steps or it is? Are there more detailed steps?

    Open app
    Navigate to Settings > Preferences > Choose Focus mode

    That didn't result in the bug on web or desktop so I'm going to remove the deploy blocker.

  7. 10 remaining items

  8. mvtglobally commented on Feb 22, 2022

    @mvtglobally
    Author

    Issue not reproducible during KI retests. (First week)

  9. mvtglobally commented on Feb 23, 2022

    @mvtglobally
    Author

    Another user has experienced this. Seems to be related to newly added drafts.
    @marcaaron Can you try if you can repro now? I was able to repro if I add 2-3 drafts and then change mode
    https://expensify.slack.com/archives/C01GTK53T8Q/p1645529273758589

  10. marcaaron commented on Feb 23, 2022

    @marcaaron
  11. marcaaron commented on Feb 23, 2022

    @marcaaron
    Contributor

    Sorry ignore previous comment. I can't repro this. Let's wait until the log fix is live and then we will have more information about what is going wrong. Please make sure to share the tester email the next time someone experiences this.

  12. self-assigned this
    on Feb 23, 2022
  13. ctkochan22 commented on Feb 23, 2022

    @ctkochan22

    Looking into this here: #7810

  14. ctkochan22 commented on Feb 24, 2022

    @ctkochan22

    The app is crashing because of our use of map() here https://github.com/Expensify/App/blame/a87b53c273be288bdc887d618973404ba01ea22b/src/pages/home/sidebar/SidebarLinks.js#L170-L174

    When we go through the list of report objects, we end up filtering out some in the next nested loop. But because map doesn't remove anything, when a report is filtered out, it returns undefined. So an array of like 8 reports will have undefined elements in them, which causes the app to crash with this error here: #7810 (comment)

    image

  15. ctkochan22 commented on Feb 28, 2022

    @ctkochan22

    It turns out that we need to use map because that is how we preserve the original order of the conversations. So we iterate through the original order, and replace those report objects with the new ones from recentReports. Pushing fixed solution now

  16. mallenexpensify commented on Mar 4, 2022

    @mallenexpensify
    Contributor

    Just happened to me, here's logs if it's helpful.
    focus mode _ crash.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions