You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Web - App crashes when selecting add new contact method #48248
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
Go to settings
Select contact method
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?
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Aug 29, 2024
Current assignee @marcaaron is eligible for the DeployBlockerCash assigner, not assigning anyone new.
melvin-bot commentedon Aug 29, 2024
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.github-actions commentedon Aug 29, 2024
👋 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:
mountiny commentedon Aug 29, 2024
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
abzokhattab commentedon Aug 29, 2024
cannot reproduce this issue
mountiny commentedon Aug 29, 2024
it was fixed on main now also fixed in staging
mountiny commentedon Aug 29, 2024
closing in favour of #48219 for payment now that this is fixed in staging too, sorry for the double issue