iOS 26.4, app 3.0.1: Integration with files app broken for WebDAV Nextcloud and MagentaCloud

[Hotziplotzi]

Summary

File app integration does not work

Please agree to the following

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

What software is involved?

• Operating System: iOS 26.4
• Cryptomator: app 2.8.3
• running data on WebDAV/Nextcloud 33

Very recently I realized that I can not access my files any longer via cryptomator on my iphone.
I do see the files listed all nice and well in the iOS files app, but when I click on them to open they do not download. The spinner symbol (the blue circle) keeps going forever.

Result is: Cryptomator is completly unusable on iOS.
I can access the same data well on both Windows and Linux systems, so it is not related to the server side or Cryptomator in general.

Volume Type

WebDAV (HTTP Address)

Steps to Reproduce

1. Open iOS files app
2. go to cryptomator
3. open folder with data, e.g. an JPG file
4. click on it to download and open
5. --> no download, no open, spinner goes on

Expected Behavior

Open the file

Actual Behavior

5. --> no download, no open, spinner goes on

Reproducibility

Always

Relevant Log Output

Anything else?

No response

[tobihagemann]

I can't relate. Just accessed a vault stored in Nextcloud via WebDAV without issues. Can you please send the log file to support@cryptomator.org? Ideally, in debug mode before you reproduce the issue, but you may have to redact sensitive information first then.

[Hotziplotzi]

I can't relate. Just accessed a vault stored in Nextcloud via WebDAV without issues. Can you please send the log file to support@cryptomator.org? Ideally, in debug mode before you reproduce the issue, but you may have to redact sensitive information first then.

Hm. I deleted my old vault and created a new one on Magentacloud with two PNG files. I have those issues from two iOS devices even with the new vault. After a lot of tries I got them to load on the phone, but that is definitely broken. I do attach the logfiles and a screenshot of an error I got after 10 seconds of waiting with the spinners turning and then clicking on the spinner.
I suggest you also create a new vault on ios 26.4 and put 10 JPGs in there and then click on each of those in the files manager. I do not expect that you can easily download all of them without issues.
My assumption is 60% that actually the issue is on Apple side with the file manager.

Logs.zip

[Hotziplotzi]

I have seen a similar bug fixed with version 3.0.1 for OneDrive and I can confirm the app works for OneDrive now again, but it still does not for Nextcloud/WebDAV or MagentaCloud/WebDAV.

Randomly some files can be openend but in 50% of cases download and using a file is impossible with the above described effects.

[j10k]

Issue appears fixed with iOS 26.4.1. I am running Cryptomator 3.0.1 1491 with a DAV share on Nextcloud 33.0.2, but the timing coincides with the iOS update.

Edited 2026-04-20: Unfortunately the issue persists. But I definitely could open more files before it occurs again than I can while it lasts. Uploads are affected as well.

[Dondo11]

iPadOS 26.4.1 w/ Cryptomator 3.0.1 (1491) and MagentaCloud WebDAV: Cannot access/copy/move Numbers file in Files app. Spinner spinning endlessly. Other files, e.g. PDF, work fine, however.

After deleting and re-adding the vault via the Cryptomator app, things are working for Numbers files, too.

I noticed the Numbers app on my MacBook was still open with no open files, “sitting” on the same vault directory I tried to access from iPadOS.

I should perhaps add that on macOS, I’m using FUSE-T (as per recommendation) to access MagentaCloud.

[voldenuit]

I’ll add this here instead of opening a new issue, as the problem might be related to WebDAV rather than a specific cloud service. I’m experiencing the exact same issue when using WebDAV with a vault stored on Infomaniak kDrive (iPadOS 26.4.1, Cryptomator 3.0.1 (1491)).

[tobihagemann]

Thank you all for your reports! I believe I was able to reproduce this issue but it was flaky. Looking into a solution right now from my own debug logs. Since it's hard for me to confirm all your reports, we'll hopefully push out an update soon and then we'll see if you all had the same root cause.