Content Unavailable error still exist with iCloud

[kyaw-sint]

Please agree to the following

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

Summary

Content Unavailable error with iCloud

System Setup

• iOS: Version 17.4
• Cryptomator: Version 2.5.1 (1212)

Cloud Type

iCloud Drive

Steps to Reproduce

1. Create vault and create files using MacBook
2. Able to read files with Cryptomator version 2.5.1 that recently updated version
3. Updated files using Cryptomator on iPhone
4. Content Unavailable error come out in particular folder that I updated on iPhone

I am using Cryptomator on iPhone and MacBook. I can able to read on iPhone what I created using MacBook after updating Cryptomator version 2.5.1 about 4 days ago. Content Unavailable error come out again after I updated the files using Cryptomator on iPhone. Please refer to attached for screenshot and log file. Kindly help on this. Thanks.

Expected Behavior

Should show the files

Actual Behavior

Content Unavailable error is shown

Reproducibility

Always

Relevant Log Output

2024/03/20 01:52:22:993  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2024/03/20 01:52:25:040  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2024/03/20 01:56:31:130  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:32:558  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:33:664  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:34:379  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:42:697  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:43:815  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:44:510  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:45:717  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:48:798  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:56:59:759  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:57:01:414  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:57:05:423  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:58:02:804  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:58:04:077  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)
2024/03/20 01:58:29:958  enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing `DELETE FROM "itemMetadata" WHERE "id" = ?` for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:85)

Anything else?

No response

[tobihagemann]

Thank you for your bug report! Can you please enable Debug Mode, trigger the error, and then send an excerpt of the relevant log file again? https://docs.cryptomator.org/en/latest/ios/settings/

Make sure to review it first and redact any sensitive information. That would help a lot!

[kyaw-sint]

I just tried to reproduce the issue again. Seems like it happen when I reshuffle with multiple folders. Meaning I have 2-3 folders and I group/put them into another new folder. Please refer to below for the logs with debug mode enabling. Thanks.

NSURLFileResourceTypeKey": NSURLFileResourceTypeDirectory, "NSURLContentModificationDateKey": 2024-03-21 11:39:35 +0000]
2024/03/21 11:39:37:991 LocalFileSystemProvider: fillCache(for: /d/DJ/5JG4TGCHPMGKRJMI6HPBGACEFWOTBD) finished
2024/03/21 11:39:37:994 enumerateItems failed with: SQLite error 19: FOREIGN KEY constraint failed - while executing DELETE FROM "itemMetadata" WHERE "id" = ? for identifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:160)
2024/03/21 11:39:38:022 FPExt: urlForItem(withPersistentIdentifier: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:160)) called
2024/03/21 11:39:38:023 FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: 53BE9135-6E4C-4748-A499-87C3ED4E668D:160)) called
2024/03/21 11:39:46:077 Deinit called for Optional(<NSFileProviderDomain: 0x10690a8a0, i{10}t id=5{34}D vid=61...01 (enabled,syncTrash,userInfo)>)

[CarST78]

I can confirm @kyaw-sint statement!

I had the problem several times that I could no longer access a folder or fault after editing it.
I have therefore logged exactly what I have done.
Delete, rename, new folder, new file: ok.
Move FILE: ok.
Move FOLDER: Error occurs.

I had the following two processes:

1. Moved a folder on the iPhone, only iPhone could read the folder in vault afterwards, iPad could not.
2. Moved a folder on the iPad, iPad suddenly could no longer access vault - during the process! Access from the iPhone is possible.
   EDIT: On 2) Cryptomator shows vault encrypted, but iOS Files App say no: Unlock your safe.

Of course, I have also tried the typical solutions: Load data completely offline, delete & reintegrate vault, delete cache, renew cloud connection, delete & reinstall Cryptomator.

Solutions | Turnaround:

1. on iPhone I created a new folder in the vault & copied the files from the damaged folder - not folder|s! himself - into it.
2. on iPhone I created a new vault and copied all files - without all folders! - here.
   (Sub|folders were therefore newly created)
   -> iPad has access again.

Unfortunately, I do not (currently) have a diagnostic file.
EDIT: @tobihagemann I can send a log on request, I still have the "defective" vault.

iOS, iPadOS: 17.5.1
Cryptomator: 2.5.2 (1228)

EDIT: Specified solutions, fault = vault