Error resolving conflict: not shown correctly when app protection is enabled

[styx-tdo]

Steps to reproduce

1. create a conflict
2. click on notification "File upload conflict"

Expected behaviour

.... conflict dialogue

Actual behaviour

get toast: Error creating conflict dialogue!

Can you reproduce this problem on https://try.nextcloud.com?

• Please create a test demo account and see if this still happens there.
• If yes, please open up a bug report
• If not, please verify server setup and ask for help on forum

Environment data

Android version: 9
Device model: BV9900Pro

Stock or customized system: stock

Nextcloud app version: 3.13.1

Nextcloud server version: 18

Reverse proxy: N/A

Logs

Web server error log

N/A

[nursoda]

Same here. Conflict dialog is not shown after tapping the notification. Instead, the error "Error creating conflict dialogue!" is shown (as toast). Device OnePlus 6T, Android 10, NC Android App 3.13.1.

Yet, some version ago it WAS shown but either choice led to the conflict not being resolved and the dialog being displayed again. For that (other) issue, see #6963

[tobiasKaminsky]

Do you have any idea what kind of conflict file this is?

[styx-tdo]

File being updated on server and client.. that this is weird for a photo folder is a question for another ticket, though.

[nursoda]

Do you have any idea what kind of conflict file this is?

In my case this happens when AutoUpload is set to COPY immediately via Wifi (don't delete locally) and I edit (crop most of the time) the image (e.g. screenshot).

[tobiasKaminsky]

Can you test #7102 ?

[stale]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[giox069]

Same problem here, with latest version (3.14.1) available on playstore of Nextcloud client for android. Phone is Huawei P10 Lite.
It started some months ago: suddenly a lot of conflicts started to appear on the InstantUpload Camera folder for no reason.
But it's impossible to open the conflict dialog/window from the system notification:

[nursoda]

Sorry, I was/am busy. Just hit the part of the error again I think. I'm on a OnePlus 6T using NC app 3.14.1 (Google Play Beta Channel) on Android 10 against NC 20.0.2. Actions to reproduce:

• set NC app to auto-upload screenshots (if resticted to only-when-charging, then plug-in cable) and to require "device credentials" ("Geräte-Anmeldedaten") to open it
• take a screenshot (I use two-button-press hotkey set in my phone settings)
• Note: On my phone, newly taken screenshots are displayed on the lower right display corner with advanced features such as "exteded screenshot" (scrolls current page down to its end and captures all of it). There, I select "edit" to crop the image (in order to share the cropped in an IM).
• edit the just-take screenshot right away (in my case crop). I see that the Nextcloud upload of the original screenshot starts in mobile phones top status bar while cropping it. Save the cropped screenshot. It's saved to the SAME filename obviously, which is intended/expected behaviour since I decided to crop it "in-place" using the above mentioned phone's feature.
• after saving, I get an NC app conflict notification. When I tap it, the NC app opens (and asks for my fingerprint) along with a toast that the "conflict dialog" could not be "created" ("Konfiktdialog konnte nicht erstellt werden" on my german phone) – and the notification disappears
• I open the NC app and head via menu to "Uploads" section. There, on the picture previews I see that the uncropped file was uploaded fine, and that the modified file is an unresolved conflict.
• tapping the conflict yields the conflict dialog (that should have displayed in the first place, so maybe it's a "dialog cannot be opened via toast when NC app access protection is enabled" issue?
• I select "new file" and "OK". The new file is uploaded and replaces the original file, so THAT part of the bug IS solved.

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[nursoda]

I don't think there is anything I could do better here since the test request above is obsolete since the subsequent reports are based on a client that already had the improvements merged.