-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Comments
same for me. Cloud Type: iCloud Drive |
Same on iOS 17.0 Beta 4 (21A5291j).
❗️ 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. |
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: which contains |
Updating to the latest iOS 17 beta, I think update 4, solved the issue so far for me. Since then, it works like expected. I assume, further information will not help. Best Bernd - mobile, short and crispyOn 5. Aug 2023, at 20:20, Philipp Schmid ***@***.***> wrote:
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 :)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please agree to the following
Summary
Unable to open Cryptomator folders in Files on iOS17 beta 3
System Setup
Cloud Type
Dropbox
Steps to Reproduce
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
The text was updated successfully, but these errors were encountered: