Skip to content

Request/Split bill - Page crash after money request/Split bill while offline #14136

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:

Preconditions: Login to yuriy.turbo+ch7@gmail.com/Aa111111

  1. Open Desktop App or Chrome Web
  2. Go Offline
  3. Make money request or Split bill
  4. Restart the App if issue is not reproduced and try again

Expected Result:

The user should be able to use Money request or Split bill while offline without any issues

Actual Result:

Page crash after money request/Split bill while offline

Workaround:

Unknown

Platforms:

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

  • Web / Chrome
  • Android app
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.2.50.13

Reproducible in staging?: Yes

Reproducible in production?: Yes

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers): yuriy.turbo+ch7@gmail.com/Aa111111

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug5889289_Screen_Recording_2023-01-09_at_12.07.49.mp4
mobizen_20230109_220400.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01ad625fac3be8adfa
  • Upwork Job ID: 1613530024908873728
  • Last Price Increase: 2023-01-12

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 9, 2023
  2. locked and limited conversation to collaborators on Jan 9, 2023
  3. melvin-bot commented on Jan 9, 2023

    @melvin-bot

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

  4. self-assigned this
    on Jan 9, 2023
  5. amyevans commented on Jan 9, 2023

    @amyevans
    Contributor

    Self-assigning. I tried a few times on prod to repro and couldn't, so I'm still curious to see if you can repro @adelekennedy (and if there are more reliable repro steps to do so). But I see the line of code where the error is from the video and should be able to add some defense against a crash. Will look into this one a bit closer later today or early tomorrow.

  6. adelekennedy commented on Jan 9, 2023

    @adelekennedy
    Contributor

    @amyevans it's not reproducible for me either, adding the needs reproducing label for additional 👀

  7. adelekennedy commented on Jan 11, 2023

    @adelekennedy
    Contributor

    hmm still not able to reproduce @amyevans did you want to take this and make it internal?

  8. amyevans commented on Jan 12, 2023

    @amyevans
    Contributor

    Sounds good!

  9. 1 remaining item

  10. unlocked this conversation on Jan 12, 2023
  11. melvin-bot commented on Jan 12, 2023

    @melvin-bot
  12. melvin-bot commented on Jan 12, 2023

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane (Internal)

  13. added and removed on Jan 13, 2023
  14. amyevans commented on Jan 23, 2023

    @amyevans
    Contributor

    Have more pressing priorities, will circle back to this as soon as possible though (but it's just clean up at this point).

  15. adelekennedy commented on Feb 2, 2023

    @adelekennedy
    Contributor

    not overdue!

  16. sobitneupane commented on Feb 2, 2023

    @sobitneupane
    Contributor

    I believe this issue is not reproducible any longer. This issue was handled in #14355 by this PR.

  17. amyevans commented on Feb 2, 2023

    @amyevans
    Contributor

    Oh nice, thanks for calling attention to that @sobitneupane. This issue definitely looks to be a dupe of #14355, which has a fixed deployed as of last week. Closing.

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.InternalRequires API changes or must be handled by Expensify staffNeeds ReproductionReproducible steps neededWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions