Skip to content
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

two accounts autoupload folder mixes content #11467

Closed
4 tasks done
tsr8 opened this issue Mar 21, 2023 · 10 comments
Closed
4 tasks done

two accounts autoupload folder mixes content #11467

tsr8 opened this issue Mar 21, 2023 · 10 comments

Comments

@tsr8
Copy link

tsr8 commented Mar 21, 2023

⚠️ 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

  1. I have two Nextcloud accounts configured on Android app.
  2. I have chosen my camera folder to autoupload on the first account.
  3. My camera folder has been sybchronized on both!
  4. Additionally some content from one account (no autoupload) infiltrate to the second one. This is big safety issue!

Expected behaviour

Accounts should be separated from each other.

Actual behaviour

Content mixes, depends on switching between two (or potentially more) accounts.

Android version

11

Device brand and model

Xiaomi mi10

Stock or custom OS?

Stock

Nextcloud android app version

3.24.1

Nextcloud server version

25.0.4

Using a reverse proxy?

No

Android logs

No response

Server error logs

No response

Additional information

No response

@tsr8 tsr8 added the bug label Mar 21, 2023
@joshtrichards
Copy link
Member

Hi @tsr8:

Couple questions to make it easier to either replicate or troubleshoot this issue:

  • Are the accounts on distinct NC servers?
  • When you select the second account profile (the one that you do not want getting your camera photos) then go to Settings -> Auto upload does your Camera folder show the cloud symbol solid (blue) or crossed out (empty)?
  • Are all camera photos being uploaded to the second account (the wrong one) or just some of them?
  • Are all camera photos being uploaded to the first account (the desired one) properly or are some missing?

@tsr8
Copy link
Author

tsr8 commented Mar 22, 2023

  • One NC server.

  • On the first acount the cloud is blue, on the second it stays grey.

  • Nearly all photos are uploaded, some missing but after long time its almoast all on two accounts. I think NC client upload photos to the selected account at the moment.

@joshtrichards
Copy link
Member

It certainly shouldn't. And, at least for me, that's not how it behaves.

  1. Do you have any auto uploads configured on the second account?
  2. Is the destination folder for the auto upload configured for sharing?

@tsr8
Copy link
Author

tsr8 commented Mar 22, 2023

  1. No.
  2. No. It synchronizes with desktop app.

@tsr8
Copy link
Author

tsr8 commented Mar 30, 2023

It's even worse now: keep uploading files to wrong account despite I have turned it off (cloud icon grayed).

@joshtrichards
Copy link
Member

Just realized this is a dup of #11088 - there's a bit more activity over there. Might want to pop over there.

@tilllt
Copy link

tilllt commented Apr 3, 2023

Yes, i have the same issue. Two accounts configured, auto upload (for camera folders) to Server 1 is enabled. Client just uploaded 6GB of my phones photos to Server 2 which DOES NOT HAVE AUTO UPLOAD ENABLED. Lucky i saw it because server 2 auto-deletes files after two weeks. This is not only a security desaster but generally a major bug.

Yeah, just to repeat the other commentators: this bug can lead to major data loss. if you have auto-upload, with delete from source enabled and a short file retention policy on one of the servers it randomly uploads to: boom your stuff is gone.

@s0riak
Copy link

s0riak commented Apr 12, 2023

I experience exactly the same issue. This is a security nightmare!

@joshtrichards
Copy link
Member

Closing in favor of consolidating the tracking of root cause analysis and progress in #11088.

@joshtrichards joshtrichards closed this as not planned Won't fix, can't repro, duplicate, stale Aug 20, 2023
@joshtrichards
Copy link
Member

Fixed in #12516 (awhile back now; just updating for those not on the other Issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants