Closed stefan0xC closed 2 months ago
I'm still having this same issue even after upgrading to 1.32 version. On iOS 17 (latest version 2024.9.2(1106)
) and also web app.
Apart from upgrading to 1.32 there's any other step to be done?
Screen shot from web console
@lapastillaroja you will have to either fix the offending item by adding the correct organization id manually in the database or remove it.
and advice on how to find the offending items?
If you are the only user of your instance just delete the latest entry (via created_at
column) otherwise you might want to restrict this to just your account (user_uuid
) or restore the latest working version from any backups you might have made.
Thank you @stefan0xC , removing the latest added item from the ciphers
table fixed the issue.
This should fix the issues reported in #4767 where an entry added via the native iOS app cannot be decrypted:
The problem seems to be that the iOS app sends an organizationID which serde fails to deseralize and because it's an optional argument adding the cipher will not fail but it will be added incorrectly to your personal vault, unless you have disabled personal ownerships. So to prevent such corruptions from occurring again I've added a reverse sanity check, just in case some other clients send the organization_id in an unrecognizable format.