Impossible to open vault after iOS 26 upgrade

[pylapp]

Summary

After iOS 26 upgrade it was impossible to open vault with FaceID the vault, like an infinite FaceID loop

Please agree to the following

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

System Setup

• iOS: 26.0
• Cryptomator: 2.7.2 (1384)

Cloud Type

No response

Steps to Reproduce

• I had previously iOS 18.6
• I upgrade to iOS 26
• I want to open my vault, FaceID asked
• FaceID successfull, but asked again
• Endless FaceID checks, vault never opened

Expected Behavior

My vault is opened

Actual Behavior

Endless FaceId checks loop, vault never opened

Reproducibility

Always

Relevant Log Output

Anything else?

Workaround

• Remove vault from Cryptmator
• Open the existing vault in Cryptomator
• Now it works

[tobihagemann]

I haven't heard of issues with an iOS 26 upgrade (haven't experienced one myself). My best guess is that the authentication token expired, and the app misbehaved due to that. Can you share with us what cloud storage service you're using? And ideally, can you find any errors inside the log file? They're accessible via the settings inside the Cryptomator app.

[pylapp]

Maybe the issue spotted after both the app update and the OS upgrade. I try do share as many details as I can.

You can find below the logs ; issue occurred around noon.

I do not use cloud storage, only local.

org.cryptomator.ios 2025-09-26--09-19-52-305

2025/09/26 09:19:52:304  Error: domainNotFound
2025/09/26 09:20:09:648  Error: domainNotFound
2025/09/26 09:20:21:356  Error: domainNotFound

org.cryptomator.ios.fileprovider 2025-09-26--08-39-45-364

2025/09/26 08:39:45:359  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:39:47:329  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:39:50:248  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:39:53:596  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:00:671  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:02:430  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:07:638  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:09:385  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:28:981  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:30:783  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:40:33:861  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:45:30:005  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:47:13:437  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 08:47:13:502  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 09:12:45:200  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 09:12:48:040  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 09:13:06:269  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 09:13:12:298  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2025/09/26 09:14:31:611  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)

org.cryptomator.ios.fileprovider-ui 2025-09-26--09-13-07-969

2025/09/26 09:13:07:968  Error: Error Domain=NSFileProviderErrorDomain Code=-1005 "Le fichier n’existe pas." UserInfo={NSFileProviderErrorNonExistentItemIdentifier=NSFileProviderRootContainerItemIdentifier, NSUnderlyingError=0x10b0621f0 {Error Domain=NSFileProviderResolverErrorDomain Code=-1011 "(null)"}}
2025/09/26 09:13:13:468  Error: Error Domain=NSFileProviderErrorDomain Code=-1005 "Le fichier n’existe pas." UserInfo={NSFileProviderErrorNonExistentItemIdentifier=NSFileProviderRootContainerItemIdentifier, NSUnderlyingError=0x11742a970 {Error Domain=NSFileProviderResolverErrorDomain Code=-1011 "(null)"}}

[tobihagemann]

That's wild. While local file systems obviously don't have authentication, there are still security mechanisms in place, required by Apple. Will look into it, thank you for reporting!

[pylapp]

Ok! If I notice such bugs and my side I will leave comments here 😁

[tobihagemann]

Since we got another report at #425 that sounds very similar, I just wanted to note: Did you already try to remove the vault from the vault list and re-add it? The other report was regarding iCloud Drive, but the mechanics under the hood using the "local file system" is similar.

[pylapp]

Yeo I removed the vault from the vaulter and added it again to be able to open my vault, as explained in my workaround 🙂

I do not remember if I did this operation before facing this issue. I can just say I did it after to solve the issue.

[tobihagemann]

Oh, I forgot that you already mentioned the workaround. Thank you for your quick feedback! I thought I didn't suggest a solution/workaround. 😅