Files wont open in Files App (The file doesn't exist)

[MRCoco22]

Steps to reproduce

1. Share Folder with user
2. Open Files App
3. Try opening File

(Under IOS 16.3 and 16.3.1 with IOS App 4.7 and 4.8 (via Testflight)

Expected behaviour

Documents should open normally and should be able to be downloaded

Actual behaviour

Pop-up message appears with following statement: "The file doesn't exist"

Screenshots

Logs

If applicable, you can post the iOS app or server logs (removing any sensitive information).

Reasoning or why should it be changed/implemented?

So users can open, Download and edit Files through the files app

Environment data

iOS version: IOS 16.3 and IOS16.3.1

Nextcloud iOS app version: see More > Settings

4.7.0.23 and 4.8.0.1

Server operating system:

Linux 5.15.74-1-pve x86_64

Web server:

Apache

Database:

mysql 10.3.36

PHP version:

7.4.32

Nextcloud version: see Nextcloud admin page

24.0.6

[marinofaggiana]

Probably something is broken ... try to restart the iPhone,

[MRCoco22]

@marinofaggiana Thx, already tried it. But the issue is on several iPads and iPhones. Indexing the users data new and re-sharing the folder doesn't seem to solve the issue either.

[saygonka]

Same issue here. Sometimes creating a new folder and copying the contents of the old folder to the new one helps, but this is not a solution to the problem.

Steps I took to fix the issue unsuccessfully:

• Rescanning files: occ files:scan --all
• Uninstalling and reinstalling the application
• Restarting the server
• Reviewing the logs (unfortunately, I didn't find anything)

Environment data

iOS version: IOS 15+

Nextcloud iOS app version:

4.7.0.23+

Server operating system:

18.04 LTS (Bionic Beaver)

Web server:

Apache

Database:

psql (10.23 (Ubuntu 10.23-0ubuntu0.18.04.1))

PHP version: 8.0.28

Nextcloud version:

24.0.11

[saygonka]

I am still researching the issue, and I came across this in the application logs: when trying to open a PDF file in the native iOS file explorer app, the first status is "200 OK", and then "404 Not Found". However, I cannot match the 404 error anywhere.

<d:multistatus>
<d:response>
<d:href>
/remote.php/dav/files/userName/BV%2012%20-%20astr%c3%9fe/Statik/01%20PB%2001%20Grundstatik%20-%20gepr%c3%bcft/Statik%20Positionsplan%2002%20DG.pdf
</d:href>
<d:propstat>
<d:prop>
<d:getlastmodified>Fri, 23 Apr 2021 06:30:57 GMT</d:getlastmodified>
<d:getetag>"609a1d6772c71"</d:getetag>
<d:getcontenttype>application/pdf</d:getcontenttype>
<d:resourcetype/>
<oc:permissions>MG</oc:permissions>
<oc:id>2938102374ocya3bx9cxde</oc:id>
<oc:fileid>2938102374</oc:fileid>
<oc:size>6523515</oc:size>
<oc:favorite>0</oc:favorite>
<oc:share-types/>
<oc:owner-id>userName</oc:owner-id>
<oc:owner-display-name>Name, user</oc:owner-display-name>
<oc:comments-unread>0</oc:comments-unread>
<oc:downloadURL/>
<oc:data-fingerprint/>
<nc:creation_time>0</nc:creation_time>
<nc:upload_time>0</nc:upload_time>
<nc:has-preview>false</nc:has-preview>
<nc:mount-type>external</nc:mount-type>
<nc:note/>
<x1:share-permissions>1</x1:share-permissions>
<x2:share-permissions>["read"]</x2:share-permissions>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<d:quota-available-bytes/>
<d:quota-used-bytes/>
<oc:checksums/>
<nc:is-encrypted/>
<nc:rich-workspace/>
<nc:lock/>
<nc:lock-owner/>
<nc:lock-owner-editor/>
<nc:lock-owner-displayname/>
<nc:lock-owner-type/>
<nc:lock-time/>
<nc:lock-timeout/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
</d:multistatus>

[AmatorPhasma]

Same issue here, on iOS/iPadOS App,

but only with files from groupfolders without share rights, for the user.

[MRCoco22]

@marinofaggiana would it be possible for you to please look into it if an opportunity opens up. Thanks very much and have a nice day :)

[marinofaggiana]

Hi, this happen with every file ?

[saygonka]

Hi, As of now, only PDFs seem to be problematic, but not all of them. When I compare the SMB Shares that are problematic with those that work, I don't find any significant differences. Furthermore, in one SMB Share, there are PDF files that can be opened via iOS File Manager and also those that cause an error.

[MRCoco22]

@marinofaggiana For our installation we see this error with all types of documents. So from MS formatted files to PDF files as stated in the issue above.

[electric-m]

Same error here on multiple iPads at school. Was working just fine a few weeks ago. Now, every time we try to save or create a file via the apple Files interface or through Pages etc. there is an error, that says, „File does not exist“.

[Kjuly1]

did anyone figure out what was causing the issue. we seem to be having the same issue with some of our students.

[SmokerCreep]

since weeks same problem on an ipad air ... seems that the background update of nextcloud is not working any more with iOS 17. If I create a new document with pages for example and will rename it same message like above [electric-m]. (pages is set to create new documnets in nextcloud root) But if you open Nextcloud App before you rename or save it in pages it is synchronized and it works ... but this should be automatically :-(

[Kri108]

Same happens here for multiple file types: File ... does not exist. The files are in a shared folder without permission to share or modify. If I add permission to modify files in the folder, it works - however I can't do that in our scenario.

Things seem to work if the files are already cached on the iPad: If you open the file in the nextcloud app and then try to open it in the files app everything works as expected.

Nextcloud App-Version 5.2.7 iPadOs-Version 17.4.1 Nextcloud Server 28.0.3 Enterprise

[fhihu]

I can confirm the last post from Kri108.

In my case, only folders can be displayed in the native iOS Location app, when the folder has been opened before in the NextCloud iOS app; otherwise I get an error "the file doesn't exist". The most problematic is, when trying to save an E-Mail Attachment to the location destination. I have to save it on local files first, then upload it via NextCloud App. I think the integration into the native iOS file system is a useful feature. This issue seems to be identically to Kri108 post. I tried to reset the app, reinstall, reconfigure the server, but nothing helped.

Furthermore, I'm on iOS 17.5.1, the first post is from March 2023. Hopefully, this get fixed soon. Thank you very much for your help and effort.

hihu

[sudoer]

Same error here, usually accessing "keepass" files using KeePassium through the iOS "files" mechanism. It's very intermittent.