Repository navigation
Crash when opening not-locally-available file #17228
Description
⚠️ Before posting ⚠️
- This is a bug, not a question or an enhancement.
- I've searched for similar issues and didn't find a duplicate.
- I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
- Browse to a markdown file that has not been previously downloaded to the device
- Click on the file to open it
- Nextcloud app crashes
See log file: nc-crash_open.md
I can explicitly download the markdown file, and then clicking on it displays the file correctly.
Then choosing edit in the menu also crashes the app.
See log file: nc-crash_edit.txt
Expected behaviour
The file should be downloaded and displayed without crashing.
It should enter edit mode of the markdown file without crashing
Actual behaviour
The app crashes
Android version
LineageOS 22.2-20260617-NIGHTLY-FP3
Device brand and model
Fairphone 3
Stock or custom OS?
Stock
Nextcloud android app version
34.0.0
Nextcloud server version
33.0.3
Using a reverse proxy?
Yes
Android logs
Server error logs
Additional information
I am having issues with WebView since the latest LineageOS update, so it could obviously be related (other apps like Wikipedia also crash at startup)
In any case, maybe the apps could better manage the issue and avoid crashing.
Since downloading manually makes it possible to display the markdown file without crashing, it could also be able to do it in one go.
Activity
alperozturk96 commentedon Aug 4, 2026
@NicolasToussaint Hey,
Could you please try with this PR once the QA APK generated?
#17422
NicolasToussaint commentedon Aug 4, 2026
Before testing the APK, I tried to reproduce with my current app (Version 34.1.0 / Sever version 34.0.2) and did not get the crash :-/
It did not crash with the test APK either.
However, I noticed that there is a "file lock" issue with original app: when editing an MD file on the phone, the file is rightfully tagged as "locked", and this is also synced on my (Linux) computer. However the "locked" tag stayed on, no way to have it removed.
I did not reproduce this with you test APK, and I could even remove the lingering lock status by editing the file again with the test APK.
One more thing: editing the file without explicitly downloading the file first does not tag the file as "locally available" (green tick) as we could expect, as it has been downloaded at some point since I can edit it. Same behaviour with both original and test APK.