Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cryptomator FileProvider doesn't authenticate on iOS17 beta 3 #318

Open
2 tasks done
davidashman opened this issue Jul 11, 2023 · 4 comments
Open
2 tasks done

Cryptomator FileProvider doesn't authenticate on iOS17 beta 3 #318

davidashman opened this issue Jul 11, 2023 · 4 comments
Labels
type:bug Something isn't working

Comments

@davidashman
Copy link

Please agree to the following

Summary

Unable to open Cryptomator folders in Files on iOS17 beta 3

System Setup

  • iOS: iOS 17 beta 3
  • Cryptomator: 2.4.9

Cloud Type

Dropbox

Steps to Reproduce

  1. Open Files app
  2. Navigate to Cryptomator FileProvider
  3. Authenticate with FaceID

Expected Behavior

Folders should open

Actual Behavior

Screen saying "Unlock required" is presented again.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@davidashman davidashman added the type:bug Something isn't working label Jul 11, 2023
@therealScarabeus
Copy link

same for me. Cloud Type: iCloud Drive

@jakubwojcik
Copy link

jakubwojcik commented Aug 1, 2023

Same on iOS 17.0 Beta 4 (21A5291j).

2023/08/01 12:53:00:348  Error: Error Domain=NSFileProviderErrorDomain Code=-2001 "No valid file provider found with identifier ‘com.apple.CloudDocs.MobileDocumentsFileProvider’." UserInfo={NSLocalizedDescription=No valid file provider found with identifier ‘com.apple.CloudDocs.MobileDocumentsFileProvider’.}

2023/08/01 12:51:25:351  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:25:353  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:25:361  FPExt: urlForItem(withPersistentIdentifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:25:361  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:25:362  FPExt: urlForItem(withPersistentIdentifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:25:362  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:26:630  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:26:646  FPExt: enumerator(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:26:646  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:51:26:654  currentSyncAnchor for NSFileProviderRootContainerItemIdentifier called -> return: Optional(CryptomatorFileProvider.SyncAnchor(invalidated: false, date: 2023-08-01 12:49:29 +0000)) 
2023/08/01 12:51:26:654  enumerateItems called for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier) - initialPage true
2023/08/01 12:51:26:655  Try to automatically unlock TestSafe - NSFileProviderDomainIdentifier(_rawValue: BC472350-A94A-492F-85DE-ED14D0F40AAE)
2023/08/01 12:51:26:691  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2023/08/01 12:51:56:594  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)
2023/08/01 12:52:53:731  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:52:53:744  FPExt: enumerator(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:52:53:745  FPExt: item(for: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)) called
2023/08/01 12:52:53:748  currentSyncAnchor for NSFileProviderRootContainerItemIdentifier called -> return: Optional(CryptomatorFileProvider.SyncAnchor(invalidated: false, date: 2023-08-01 12:49:29 +0000)) 
2023/08/01 12:52:53:748  enumerateItems called for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier) - initialPage true
2023/08/01 12:52:53:749  Try to automatically unlock TestSafe - NSFileProviderDomainIdentifier(_rawValue: BC472350-A94A-492F-85DE-ED14D0F40AAE)
2023/08/01 12:52:53:775  enumerateItems getAdapter failed with: defaultLock for identifier: NSFileProviderItemIdentifier(_rawValue: NSFileProviderRootContainerItemIdentifier)

❗️ You can actually do a workaround and add your safe again (Cryptomator -> Vaults -> "+" Icon -> Open Existing Vault -> Select Storage Provider -> Select Vault Folder).

It seems to me that between iOS 16 and 17 there were changes in FileProviderAPI and re-registering the safe in the "Files" via the Cryptomator app solves this problem.

@phil1995
Copy link
Collaborator

phil1995 commented Aug 5, 2023

It seems to me that between iOS 16 and 17 there were changes in FileProviderAPI and re-registering the safe in the "Files" via the Cryptomator app solves this problem.

Thanks for the insights! This would also explain why I can't reproduce this in the simulator. Unfortunately I have to admit that I have no clue what's causing this by just reading the posted logs. Can you check if you have something under:
iOS settings -> Privacy -> Analytics & Improvements -> Analytics data

which contains fileprovider or Cryptomator?
This would help us a lot to better pinpoint the root cause. Because maybe the FileProvider crashes while unlocking a vault which has been created with something older than iOS 17.
Thanks in advance :)

@therealScarabeus
Copy link

therealScarabeus commented Aug 5, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants