Skip to content

[HOLD for payment 2023-10-12] [HOLD for payment 2023-10-10] [$500] Web - App crash on click of back button #28634

Closed

Description

@kbecciv

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. Go to Settings > Workspaces
  2. Click on back button

Expected Result:

App should not crash

Actual Result:

App crash (Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate)

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: Dev 1.3.75-8
Reproducible in staging?: n
Reproducible in production?: n
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
Notes/Photos/Videos: Any additional supporting documentation

Screen.Recording.2023-10-02.at.1.03.28.PM.mov

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696231998119979

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~015b1efa830b9ecb1c
  • Upwork Job ID: 1708892554706366464
  • Last Price Increase: 2023-10-02

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 2, 2023
  2. changed the title [-]Dev: Web - App crash on click of back button[/-] [+][$500] Dev: Web - App crash on click of back button[/+] on Oct 2, 2023
  3. melvin-bot commented on Oct 2, 2023

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 2, 2023
  5. melvin-bot commented on Oct 2, 2023

    @melvin-bot

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

  6. MonilBhavsar commented on Oct 2, 2023

    @MonilBhavsar
    Contributor

    Potential deploy blocker when #27223 is deployed

  7. shubham1206agra commented on Oct 2, 2023

    @shubham1206agra
    Contributor

    This should be treated as a regression
    @kacper-mikolajczak Can you fix this ASAP?

  8. situchan commented on Oct 2, 2023

    @situchan
    Contributor

    That PR caused another bad regression - #27223 (comment)
    I think better to revert as it's just function component refactor.

  9. situchan commented on Oct 2, 2023

    @situchan
    Contributor

    @ArekChr and @kacper-mikolajczak will handle this

  10. changed the title [-][$500] Dev: Web - App crash on click of back button[/-] [+][$500] Web - App crash on click of back button[/+] on Oct 2, 2023
  11. 25 remaining items

  12. melvin-bot commented on Oct 17, 2023

    @melvin-bot

    @francoisl, @hoangzinh Whoops! This issue is 2 days overdue. Let's get this updated quick!

  13. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 17, 2023
  14. melvin-bot commented on Oct 17, 2023

    @melvin-bot

    Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  15. melvin-bot commented on Oct 17, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  16. francoisl commented on Oct 17, 2023

    @francoisl
    Contributor

    This blocker was handled internally, so I believe we just need to compensate @gadhiyamanan for reporting the issue.

  17. mallenexpensify commented on Oct 18, 2023

    @mallenexpensify
    Contributor

    Thanks @francoisl
    @gadhiyamanan , can you please accept the job and reply here once you have?
    https://www.upwork.com/jobs/~015b1efa830b9ecb1c

    (d'oh, thought I was BZ here, hahahah)

  18. gadhiyamanan commented on Oct 18, 2023

    @gadhiyamanan
    Contributor

    @mallenexpensify offer accepted, thanks!

  19. mallenexpensify commented on Oct 18, 2023

    @mallenexpensify
    Contributor

    Issue reporter: @gadhiyamanan paid $50 via Upwork

    @hoangzinh can you fill out the below please, not sure why it wasn't auto-posted here.

    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:

    • The PR that introduced the bug has been identified. Link to the PR:
    • 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:
    • 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:
    • 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.
    • Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  20. hoangzinh commented on Oct 19, 2023

    @hoangzinh
    Contributor

    BugZero Checklist:

  21. hoangzinh commented on Oct 19, 2023

    @hoangzinh
    Contributor

    @mallenexpensify Oh wait. Do we still need the BZ checklist? This issue was handled internally by reverting the offending PR.

  22. mallenexpensify commented on Oct 20, 2023

    @mallenexpensify
    Contributor

    oh, I think I missed that @hoangzinh , I don't think we need the BZ checklist if we reverted the PR. Thx!

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions