Skip to content

Web - Workspace - Error message "There was a problem adding this workspace member" displayed when adding non-existing account #11595

Closed

Description

@kbecciv

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. Go to staging.new.expensify.com
  2. Log in with your account
  3. Go to Setting - Workspace.
  4. Click Manage members.
  5. Click on Invite.
  6. Add a non-existent user and click Invite.

Expected Result:

No error message "There was a problem adding this workspace member" and console error when adding non-existing account

Actual Result:

Error message "There was a problem adding this workspace member when adding non-existing account

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.2.11.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers): any

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Recording.1320.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Oct 4, 2022

    @melvin-bot

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

  2. melvin-bot commented on Oct 10, 2022

    @melvin-bot

    @puneetlath Eep! 4 days overdue now. Issues have feelings too...

  3. puneetlath commented on Oct 10, 2022

    @puneetlath
    Contributor

    It looks like this most likely has to do with inviting a member on a Domain Controlled domain, so will need to be Internal.

  4. added
    InternalRequires API changes or must be handled by Expensify staff
    on Oct 10, 2022
  5. melvin-bot commented on Oct 14, 2022

    @melvin-bot

    @puneetlath Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  6. melvin-bot commented on Oct 18, 2022

    @melvin-bot

    @puneetlath Still overdue 6 days?! Let's take care of this!

  7. puneetlath commented on Oct 19, 2022

    @puneetlath
    Contributor

    Still expecting to get to this this week.

  8. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 19, 2022
  9. melvin-bot commented on Oct 25, 2022

    @melvin-bot

    @puneetlath Huh... This is 4 days overdue. Who can take care of this?

  10. puneetlath commented on Oct 25, 2022

    @puneetlath
    Contributor

    It looks like the problem is happening here, where we try to get the authToken for the closed accounts in order to push the policy reports into their Onyx data. So we should only do that if the account is open.

  11. puneetlath commented on Oct 25, 2022

    @puneetlath
    Contributor

    PR sent.

  12. puneetlath commented on Oct 28, 2022

    @puneetlath
    Contributor

    PR has been merged.

  13. melvin-bot commented on Nov 1, 2022

    @melvin-bot

    @puneetlath Whoops! This issue is 2 days overdue. Let's get this updated quick!

  14. puneetlath commented on Nov 1, 2022

    @puneetlath
    Contributor

    This was deployed to production yesterday.

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.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions