bitwarden
"Resource not found" trying to share a login to organization
My family has one organization, with one shared collection. Tonight my wife created her account in response to my organization invitation. Once I had confirmed her on the organization, she could see the org and the collection. She tried to share a login to the collection by clicking "Share" from the item's gear menu in the web UI. The share form looked as expected; she checked the box for our collection and clicked the "Share" button.... and got a "Resource not found" error message.
I tried upgrading her from user to admin, no change. I wish I knew WHAT resource it couldn't find...
I still have this issue. If this is a bug as you say it is why hasn't this been fixed yet since 2017? https://cl.ly/b503c4207f1b
Just encountered this as well. Free tier, added a second person, they ran into the above issue. I found this bug report and had them log out and log back in. That worked. Should this issue be reopened? Should I made a new one?
I just reproduced this with the same two users but going in the other direction. You must log out after accepting an invite (and perhaps it has to be after the inviter confirms you on their end?).
I can confirm this also happens at the Bitwarden site as well. Logging out solves the issue.
I experienced this issue today. A logout resolved the problem, but this is clearly poor UX. Why is this bug closed?
Confirming ran into this issue today. Logging out/in fixed it, but that isn't the best solution to this.
Happens for me as well: https://github.com/bitwarden/browser/issues/1534#issuecomment-839205452. A log out and a log back in fixes the issue. Cc @kspearrin. This is a pretty bad UX issue for someone coming into the platform for the first time and is thinking if they want to stick around or not. I imagine most users will end up in this GH issue. Hope you fix soon : )
I'm reopening this because it's still a bug, even if it's a known one. In my experience, the same thing happens when trying to save an item to a collection, if the user has not logged out and back in again since being confirmed to that org.
The problem appears to be that the server uses the currentContext object to track what org membership a user has, and this is not updated until the user logs out and back in.
Still an issue today, when adding a user to an organisation it will give a "Resource not found" error until they log out and log back in. Any word on a fix?
Hi, @wearepariah! I tried to replicate it with no luck. But I mark it as a bug in our internal tool to investigate it better and fix it as soon as we can.
Still a thing. Invited a account to an organisation and the new account is not able to add a login to a collection of the orgranisation. LogOut and LogIn fixed it.
6 years and same problem... wow logout/login does not help...
regretting resubscription already
