Skip to content

Web - App crashes when selecting add new contact method #48248

Closed

Description

@mountiny

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:
Reproducible in staging?:
Reproducible in production?:
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:
Slack conversation:

Action Performed:

Break down in numbered steps

  1. Go to settings
  2. Select contact method
  3. Click to add a new contact method

Expected Result:

Describe what you think should've happened

new page loads

Actual Result:

Describe what actually happened

App crashes

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Add any screenshot/video evidence

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 29, 2024
  2. melvin-bot commented on Aug 29, 2024

    @melvin-bot

    Current assignee @marcaaron is eligible for the DeployBlockerCash assigner, not assigning anyone new.

  3. melvin-bot commented on Aug 29, 2024

    @melvin-bot

    Triggered auto assignment to @puneetlath (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 Aug 29, 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. mountiny commented on Aug 29, 2024

    @mountiny
    ContributorAuthor

    Shoot I did not see there was already issue created #48219 I should have just added the blocker label on that, the bug was already in staging

  6. added
    ReviewingHas a PR in review
    and removed on Aug 29, 2024
  7. abzokhattab commented on Aug 29, 2024

    @abzokhattab
    Contributor

    cannot reproduce this issue

  8. mountiny commented on Aug 29, 2024

    @mountiny
    ContributorAuthor

    it was fixed on main now also fixed in staging

  9. mountiny commented on Aug 29, 2024

    @mountiny
    ContributorAuthor

    closing in favour of #48219 for payment now that this is fixed in staging too, sorry for the double issue

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.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions