Google Drive unlock fails when vault parent folder has an apostrophe

[AliSalman-et-al]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Google Drive unlock fails when vault parent folder has an apostrophe

System Setup

• iOS: 16.2
• Cryptomator: 2.4.4 (previously Cryptomater 2)

Cloud Type

Google Drive

Steps to Reproduce

1. Create a vault on Google Drive on account "A" with a name containing a apostrophe "A'22 Resource"
2. Add account "B" as a viewer onto the vault using Google Drive
3. Use Cryptomater and proceed with adding existing shared vault from Google Drive using account "B"
4. Enter the passphrase to add the vault and click open in Files
5. When entering the passphrase again to unlock the vault in Files it fails showing invalid passphrase

I have also found another issue present on the latest Cryptomater (previously Cryptomater 2) iOS Version 2.4.4. When using an apostrophe character in the name of the parent folder containing the vault on Google Drive. Cryptomater can successfully accept password to add the vault, however displays “failed with error: invalidPassphrase” when using the same password to unlock in the “Files” app. Removing the apostrophe from the parent folder name to just leave letters, numbers, and a space in the name fixed it.

Expected Behavior

Cryptomater vault should unlock displaying the content in the Files app

Actual Behavior

Cryptomater breaks showing "failed with error: invalidPassphrase” in the logs.

Reproducibility

Always

Relevant Log Output

2023/01/19 12:49:25:955  Opening existing vault "D'27 Resources" (749B1D6D-57B7-40A9-A665-222364601342) failed with error: invalidPassphrase
2023/01/19 13:02:09:639  Setting trialExpirationDate was removed
2023/01/19 13:02:09:639  Setting fullVersionUnlocked was written with value false
2023/01/19 13:02:09:639  Setting hasRunningSubscription was written with value false
2023/01/19 13:02:11:194  Setting trialExpirationDate was removed
2023/01/19 13:02:11:194  Setting fullVersionUnlocked was written with value false
2023/01/19 13:02:11:194  Setting hasRunningSubscription was written with value false
2023/01/19 13:03:04:332  Setting trialExpirationDate was removed
2023/01/19 13:03:04:332  Setting fullVersionUnlocked was written with value false
2023/01/19 13:03:04:332  Setting hasRunningSubscription was written with value false
2023/01/19 13:03:20:363  Setting trialExpirationDate was removed
2023/01/19 13:03:20:364  Setting fullVersionUnlocked was written with value false
2023/01/19 13:03:20:364  Setting hasRunningSubscription was written with value false
2023/01/19 13:04:52:928  Setting trialExpirationDate was removed
2023/01/19 13:04:52:928  Setting fullVersionUnlocked was written with value false
2023/01/19 13:04:52:928  Setting hasRunningSubscription was written with value false
2023/01/19 13:04:56:787  Setting trialExpirationDate was removed
2023/01/19 13:04:56:787  Setting fullVersionUnlocked was written with value false
2023/01/19 13:04:56:787  Setting hasRunningSubscription was written with value false
2023/01/19 13:05:34:089  Freemium version
2023/01/19 13:05:34:103  Setting trialExpirationDate was removed
2023/01/19 13:05:34:103  Setting fullVersionUnlocked was written with value false
2023/01/19 13:05:34:103  Setting hasRunningSubscription was written with value false
2023/01/19 13:05:34:335  Setting trialExpirationDate was removed
2023/01/19 13:05:34:335  Setting fullVersionUnlocked was written with value false
2023/01/19 13:05:34:335  Setting hasRunningSubscription was written with value false
2023/01/19 13:05:34:886  Setting trialExpirationDate was removed
2023/01/19 13:05:34:886  Setting fullVersionUnlocked was written with value false
2023/01/19 13:05:34:886  Setting hasRunningSubscription was written with value false
2023/01/19 13:05:35:841  Setting trialExpirationDate was removed
2023/01/19 13:05:35:842  Setting fullVersionUnlocked was written with value false
2023/01/19 13:05:35:842  Setting hasRunningSubscription was written with value false
2023/01/19 13:05:36:804  Setting debugModeEnabled was written with value false
2023/01/19 13:05:51:373  Setting trialExpirationDate was removed
2023/01/19 13:05:51:373  Setting fullVersionUnlocked was written with value false
2023/01/19 13:05:51:373  Setting hasRunningSubscription was written with value false
2023/01/19 13:05:53:078  Setting trialExpirationDate was removed
2023/01/19 13:05:53:078  Setting fullVersionUnlocked was written with value false
2023/01/19 13:05:53:078  Setting hasRunningSubscription was written with value false

Anything else?

This problem was fixed after renaming the vault parent folder, removing the apostrophe to just leave letters, numbers, and a space.

Additional logs have been submitted on the Skymatic Helpdesk Ticket#82304