-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
upload duplicated file does not open conflict dialog #6027
Comments
Yep, the conflict dialog should be opened immediately, before any upload is taking place. :) |
yes, it should |
This is not as easy as I hoped, as uploader is done in background. Imagine you upload 10 files, and the 10th has a conflict, then it would pop up while you are maybe already at an entire different place in the app. Checking it immediately is also not a reliable way, imagine you upload again 10 large files
We then need to have both. |
Or do you have better ideas? :-) |
I'm also facing the same issue, I'm on app version 3.13.0 Please let me know if I can do something to help (not a android developer tho..) |
I've been having this issue for a while too |
Tested and works on master, so it will be in 3.14 RC2 |
I have 3.14.0 and still have this issue |
Same, this is still an issue for me. I have constant issues with video files being marked as conflicts by the app, I assume it's due to their size somehow messing up the upload process. It's frankly infuriating, as the only way to deal with it is to manually open the app, find the uploads tab and tap the X by each file. Far from hands off automatic upload. Also, no conflict dialog and an error as above. |
I have 3.14.1 and also the bug |
What is this can u give me a the reason of this site
On Sat, Dec 26, 2020 at 1:03 AM malo ***@***.***> wrote:
I have 3.14.1 and also the bug
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6027 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASHRCGRZFTCWIJEJ4VX3Z4DSWT423ANCNFSM4M4EIDIA>
.
--
--
*Thank You & Regards**,*
*Meca Salas* |
|
I am still having this issue with app version 3.15.1 on Android 10. The Nextcloud server version is 20.0.8 (stable branch, still waiting for Nextcloud 21 to be offered) |
Please reopen, I too have this error in app v. 3.15.1 and server 20.0.9 |
Same for me with app v.3.15.1 and server v.21.0.1 |
Same issue, app version 3.16.1 |
I use the auto upload feature to upload my Signal backups, and I'm experiencing this issue as well. App 3.16.1, server 21.0.2. Here's the logcat: https://gist.github.com/escarlson/fa20201d4aa8e463d8551ff26b00b5d5 |
App 3.17.1 Server 22.2.0 I'm having this problem several times a day. Any updates? |
@tobiasKaminsky please re-open this issue, as this is not fixed as of 3.18.1. |
Can confirm it is still an issue as of 3.18.1 |
I confirm "cannot open conflict dialogue" issue with latest android nextcloud app on android 11 and nextcloud server hosted on centos 8 as i notice it seems to happen with mp4 files only |
sorry, didn't see your edits - so logs from yesterday won't be available anymore? If the error shows up again I'll share my logs 👍 |
I'm unable to get rid of these messages at all. So, in my case I don't need to wait for the event to happen. I haven't found a way to save logs to submit them here. If you could please share an instruction. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I'd like to reopen this bug. The issue still occurs Android app: 3.20.1 I cannot upload any file through the Nextcloud Android app anymore. Every time I get the error message that there is a File conflict -- which there is definitely not. Then when I try to open the duplicated file dialog, the 'Error creating conflict dialog` is thrown Logcat log:
|
I too see failed uploads which fail to open the conflicts dialog, and
client version 3.20.1 The unusual thing here is that these failed uploads all reside on an SFTP external storage (hetzner storagebox), which in the past had problems with big uploads to nextcloud appearing on the storage, but nextcloud not recognizing them as done and thus the client endlessly retrying to upload. |
I have a logcat log of the message. It keeps bugging me for one specific file.
Edit by repo admin: edited for readability |
Same issue here app version 3.21.2 |
Gosh, I was getting desperate, with 1000+ notifications a day, until I figured out what file it was causing problems. I had conflicts before, and they were easy to fix. But now it just shows the "error creating conflict dialogue", therefore the conflict can't be solved and the warning keeps poping up, non-stop. I'm on version 3.22.1 (f-droid). I was using a previous version when this started, some days ago, I updated it but the problem remains. I also use hetzner host (maintained by them, server version 24.0.5), as mentioned above, not sure if it is a coincidence. |
I can confirm the problem still exists in 3.26.0. Keeps reporting conflicts, with no way to resolve them. |
Also experiencing this problem. Deleting the on-device file doesn't stop the conflict notifications either. Android 14 UP1A.231005.007.2023101300 |
Still a problem. Restarting the phone does not fix it. Restarting the server does not fix this either. Nextcloud Android ver 3.26.0 |
I decided to switch to Syncthing for synchronizing my photos since this problem makes Nextcloud unusable. |
Oh, it's the first time I get this error too. Can not decide which uploads to keep. The notification is spamming me right now. |
Getting this error as well. |
Can confirm, I just installed the app, and I get popups about sync conflicts. But when I try to open it, I get "Error creating conflict dialog" |
Issue still exist in 3.27.0 :-( |
I can confirm the issue "error creating conflict dialog" |
If you do not have an app passcode set and you're experiencing this behavior today, let us know here. If you do have app protection (app passcode) enabled, #7000 is the issue you want. |
Steps to reproduce
-> does not open direct conflict dialog
Expected behaviour
Actual behaviour
@AndyScherzinger @jancborchardt correct, or?
The text was updated successfully, but these errors were encountered: