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
Version Number: 9.0.26-1 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail:https://expensify.testrail.io/index.php?/tests/view/4900428 Email or phone of affected tester (no customers):fischer9966 [email protected] Issue reported by: Applause Internal Team
Action Performed:
Open App or go to staging.new.expensify.com
Login with any account
Go to Settings > Profile > Contact Methods
Tap/Click on "New contact method" button
Expected Result:
"Email/Phone number" page opens
Actual Result:
App crashes after tap on Settings > Profile > Contact Methods > "New Contact Method"
👋 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.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.26-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4900428
Email or phone of affected tester (no customers): fischer9966 [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
"Email/Phone number" page opens
Actual Result:
App crashes after tap on Settings > Profile > Contact Methods > "New Contact Method"
Workaround:
Unknown
Platforms:
Screenshots/Videos
2908_1.txt
Bug6585898_1724886023509.Web-App-Crash-New-Contact-Method.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: