Skip to content

Security - Endless spinner when try to close account #20955

New issue
New issue
Closed
Closed
Security - Endless spinner when try to close account#20955
Assignees
slafortunemarcaaron
Labels
BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringNeeds ReproductionReproducible steps needed

Description

@lanitochka17
lanitochka17
opened on Jun 17, 2023

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 http://staging.new.expensify.com/
  2. Log into a new account (expensifail and gmail)
  3. Go to Settings > Security > Close account
  4. Enter default contact method
  5. Tap on "Close account" button

Expected Result:

Account should be close.

Actual Result:

Endless spinner is diaplayed when try to close account.

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: 1.3.29.0

Reproducible in staging?: Yes

Reproducible in production?: No

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

Bug6096207_close.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. lanitochka17
    added
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 17, 2023
  2. github-actions
    added
    Engineering
    HourlyKSv2
    on Jun 17, 2023

  3. OSBotify commented on Jun 17, 2023

    @OSBotify
    OSBotify
    on Jun 17, 2023
    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.
  4. melvin-bot
    assigned
    marcaaron
    on Jun 17, 2023

  5. melvin-bot commented on Jun 17, 2023

    @melvin-bot
    melvin-botBot
    on Jun 17, 2023

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

  6. melvin-bot
    added
    Overdue
    on Jun 19, 2023

  7. marcaaron commented on Jun 19, 2023

    @marcaaron
    marcaaron
    on Jun 19, 2023
    Contributor

    Email or phone of affected tester (no customers):

    Please fill this out. If this issue is related to the account you are using it can help us identify the cause.

  8. melvin-bot
    removed
    Overdue
    on Jun 19, 2023

  9. marcaaron commented on Jun 19, 2023

    @marcaaron
    marcaaron
    on Jun 19, 2023
    Contributor

    I think we can make it a non-blocker as I'm unable to reproduce on staging.

  10. marcaaron
    added
    DailyKSv2
    Needs ReproductionReproducible steps needed
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    HourlyKSv2
    on Jun 19, 2023

  11. melvin-bot commented on Jun 19, 2023

    @melvin-bot
    melvin-botBot
    on Jun 19, 2023

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

  12. melvin-bot
    assigned
    slafortune
    on Jun 19, 2023

  13. melvin-bot commented on Jun 19, 2023

    @melvin-bot
    melvin-botBot
    on Jun 19, 2023

    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

  14. slafortune commented on Jun 21, 2023

    @slafortune
    slafortune
    on Jun 21, 2023
    Contributor

    Not able to reproduce - closed stevielafortune@gmail.com successfully
    Checking for updates
    Chrome Version 114.0.5735.133 (Official Build) (x86_64)
    MacOS 13.3.1 (22E261)

  15. slafortune commented on Jun 21, 2023

    @slafortune
    slafortune
    on Jun 21, 2023
    Contributor

    @lanitochka17 are you able to reproduce this?

  16. lanitochka17 commented on Jun 21, 2023

    @lanitochka17
    lanitochka17
    on Jun 21, 2023
    Author

    @slafortune Not reproduce. Issue fixed

    not.mp4

  17. slafortune commented on Jun 22, 2023

    @slafortune
    slafortune
    on Jun 22, 2023
    Contributor

    Thanks @lanitochka17

  18. slafortune
    closed this as completedon Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringNeeds ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions