Tom Raganowicz

I didn't have time to investigate the issue exactly however it seems that actually both: `sodium.crypto.aeadAes256Gcm.decrypt` and `sodium.crypto.aeadAes256Gcm.encrypt` functions are failing on a real Android device with: "A low-level libsodium...

That's really great to hear. Is it possible by any chance that this change also resolves the: "A low-level libsodium operation has failed" for AES on a real Android device?

I was wondering if solution mentioned here: https://github.com/rclone/rclone/issues/7345#issuecomment-1821463100 Replace: https://github.com/rclone/rclone/blob/master/fs/operations/operations.go#L119 ```golang return srcHash == dstHash, ht, srcHash, dstHash, nil ``` with ```golang return strings.ToUpper(srcHash) == strings.ToUpper(dstHash), ht, srcHash, dstHash, nil...

I've created pull request: https://github.com/henrybear327/Proton-API-Bridge/pull/27 but given that I couldn't exactly reproduce this issue (no idea in which case Proton would return uppercase SHA1 instead of lowercased one) it is...