"Grantee user already invited" not shown in Web Vault #2258

Closed
opened 2026-02-05 03:44:16 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @Saviq on GitHub (May 10, 2025).

Vaultwarden Support String

N/A

Vaultwarden Build Version

2025.1.1

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

haproxy

Host/Server Operating System

Linux

Operating System Version

No response

Clients

Web Vault

Client Version

No response

Steps To Reproduce

  1. Go to 'Emergency Access'
  2. Click on 'Add emergency contact'
  3. Try adding an existing emergency contact

Expected Result

Error displayed

Actual Result

Nothing, response is:

{
  "error": "",
  "errorModel": {
    "message": "Grantee user already invited: ...",
    "object": "error"
  },
  "error_description": "",
  "exceptionMessage": null,
  "exceptionStackTrace": null,
  "innerExceptionMessage": null,
  "message": "Grantee user already invited: ...",
  "object": "error",
  "validationErrors": {
    "": [
      "Grantee user already invited: ..."
    ]
  }
}

Logs


Screenshots or Videos

No response

Additional Context

No response

Originally created by @Saviq on GitHub (May 10, 2025). ### Vaultwarden Support String N/A ### Vaultwarden Build Version 2025.1.1 ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy haproxy ### Host/Server Operating System Linux ### Operating System Version _No response_ ### Clients Web Vault ### Client Version _No response_ ### Steps To Reproduce 1. Go to 'Emergency Access' 2. Click on 'Add emergency contact' 3. Try adding an existing emergency contact ### Expected Result Error displayed ### Actual Result Nothing, response is: ```json { "error": "", "errorModel": { "message": "Grantee user already invited: ...", "object": "error" }, "error_description": "", "exceptionMessage": null, "exceptionStackTrace": null, "innerExceptionMessage": null, "message": "Grantee user already invited: ...", "object": "error", "validationErrors": { "": [ "Grantee user already invited: ..." ] } } ``` ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_
OVERLORD added the bug label 2026-02-05 03:44:16 +03:00
Author
Owner

@BlackDex commented on GitHub (May 10, 2025):

Why would you try to add an existing emergency contact?
Did the invited user accepted the invite already?
Did you tried to logout and login again?

@BlackDex commented on GitHub (May 10, 2025): Why would you try to add an existing emergency contact? Did the invited user accepted the invite already? Did you tried to logout and login again?
Author
Owner

@Saviq commented on GitHub (May 10, 2025):

Why would you try to add an existing emergency contact?

By mistake. In fact, the contact got added when I first pressed the button, without feedback, and subsequent tries yielded the above error.

I'll verify / reproduce and file a separate issue for that.

Did the invited user accepted the invite already?

No.

@Saviq commented on GitHub (May 10, 2025): > Why would you try to add an existing emergency contact? By mistake. In fact, the contact got added when I first pressed the button, without feedback, and subsequent tries yielded the above error. I'll verify / reproduce and file a separate issue for that. > Did the invited user accepted the invite already? No.
Author
Owner

@BlackDex commented on GitHub (May 10, 2025):

Well adding a user twice would result in that error and would be correct of course.

I actually think it would be resolved already in the testing tagged images.

@BlackDex commented on GitHub (May 10, 2025): Well adding a user twice would result in that error and would be correct of course. I actually think it would be resolved already in the `testing` tagged images.
Author
Owner

@Saviq commented on GitHub (May 10, 2025):

Well adding a user twice would result in that error and would be correct of course.

But it's not displayed in the Vault UI, that's what the bug is about.

I actually think it would be resolved already in the testing tagged images.

I'll check and report back.

@Saviq commented on GitHub (May 10, 2025): > Well adding a user twice would result in that error and would be correct of course. But it's not displayed in the Vault UI, that's what the bug is about. > I actually think it would be resolved already in the `testing` tagged images. I'll check and report back.
Author
Owner

@BlackDex commented on GitHub (May 10, 2025):

Yes, and that isn't something we can fix. We do not maintain or develop the clients.

@BlackDex commented on GitHub (May 10, 2025): Yes, and that isn't something we can fix. We do not maintain or develop the clients.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#2258