Repository navigation
Profile - User is asked to verify new created workspace as contact method. #58606
Description
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: 9.1.14-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): ibellicotest+410@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: User Settings
Action Performed:
- Open the staging.new.expensify.com website.
- Sign up with a new account.
- Complete the onboarding modal selecting "Track and budget expenses" option.
- Tap on the FAB and select "New Workspace"
- Confirm the workspace creation.
- Navigate to "Settings" and tap on "Profile"
- Tap on "Contact Method"
- Check that the user is asked to verify the created workspace as contact method.
Expected Result:
User should only be asked to verify Emails as contact methods.
Actual Result:
After creating a workspace, a "@expensify-policy" option is displayed in profile section, to verify as contact method.
Workaround:
Unknown
Platforms:
- Android: Standalone
- Android: HybridApp
- Android: mWeb Chrome
- iOS: Standalone
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Activity
melvin-bot commentedon Mar 18, 2025
Triggered auto assignment to @dylanexpensify (
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.melvin-bot commentedon Mar 18, 2025
Triggered auto assignment to @jasperhuangg (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 18, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Mar 18, 2025
👋 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:
mitarachim commentedon Mar 18, 2025
issue not reproduce in STG while
Use Staging ServerisOFF2025-03-18.7.49.18.AM.mp4
jasperhuangg commentedon Mar 18, 2025
From the above comment this doesn't need to be an App deploy blocker
jasperhuangg commentedon Mar 18, 2025
This is a dupe of #57728, which also has already happened on production. Closing in favor of that one, and also we don't need to block Web deploy on this either