Hopefully posting to the right area… (apologies if not).
The most recent version of the IOS app (2.5.1) on IOS 26.2 has an issue. It took a good bit of testing to try to figure out -what- the actual error meant and/or what it pertained to. Eventually realizing that it only occurs on folders that are “shared”. The server is CE 5.8.0 - ensured that everything was up to date this evening as part of trying to determine the issue. Runs on a Debian bookworm instance with php8.2 - healthcheck passes, states passbolt ce is on latest.
Issue description:
Very small (self hosted) instance with <10 users. Each user shares a couple password folders with 1+ other users or to a “group”. In testing, all of the following fail with the same error (shown below):
- Folder shared by owner to a single user, read only
- Folder shared by owner to a single user, can update
- Folder shared by owner to a group, read only
- Folder shared by owner to a group, can update
- (did not test other possible combinations, as they aren’t used in this scenario)
For all folders being “shared”, the user (owner) is unable to edit any of their own entries in the Folder (via the IOS app, but works just fine via web browser). When they tap the three circles and then select “Edit” at the bottom, they receive the message: “You cannot perform this action because you lack access to the shared metadata key.” The error flashes briefly at the bottom of the screen, with a red background and then disappears. The moment the Folder is not “shared” - the user is able to edit any of their records (that they originally created) within the Folder, via the IOS passbolt app. For clarity, ALL of the records in the Folder were created by the -same- user, that is now prohibited from modifying their records if the Folder is “shared”. This does not happen when working with a web browser (Librewolf, as example) - the user is able to modify their records. As this configuration (shared folders) has been utilized for quite a while (well prior to 5.x) - don’t recall this issue being present previously with the IOS app. (Admittedly, most changes are via browser with changes via the IOS app being infrequent. IOS app is mostly used to ‘copy’ a password for use and not ‘update’ records).
Unable to express -when- this error started happening, as a recent attempt to change a record brought this issue to awareness.
Hopefully someone here may have already encountered this error and knows how to correct it.
Thanks!