Skip to content

Auto-upload settings were reset #14931

Closed
Closed
Auto-upload settings were reset#14931
Assignees
alperozturk96
Labels
bug

Description

@thaytan
thaytan
opened on May 29, 2025

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

I noticed last night that my Auto-uploads were no longer working, and had missed 5 days of new photos and videos. This might have happened in 3.31.3 RC1 ?

When I checked the settings, all the configuration for Photo/Video upload folders had be reset to default: Disabled, configured to send everything to InstantUploads, and without the setting to sort things into folders.

When I re-enabled it, Nextcloud failed to notice and auto-upload the new photos/videos. I had to add them manually.

Expected behaviour

Nextcloud should not lose Auto-upload settings

Actual behaviour

At some point about 5 days ago, Nextcloud quietly reset my auto-upload settings and stopped auto-uploading anything.

Android version

15

Device brand and model

Google Pixel 7 Pro

Stock or custom OS?

Stock

Nextcloud android app version

3.31.3

Nextcloud server version

31.0.2

Using a reverse proxy?

No

Android logs

No response

Server error logs



Additional information


No response
Activity
  1. thaytan
    added 
    bug
     
    0. Needs triage
     on May 29, 2025
  2. bryanlougheed commented on May 29, 2025 
    @bryanlougheed
    bryanlougheed
    on May 29, 2025
    Same happened to me, expect my entire app reset after an update and I had to add the account again. It directs my to my nextcloud website to sign in. After the sign in is successful, I am directed back to the app and get the error below. Anybody know how I can download the older version of the app, this version seems to be bricked.
    

    Cause of error
    

    Exception in thread "main" java.lang.SecurityException: uid 10377 cannot explicitly add accounts of type: nextcloud
    at android.os.Parcel.createExceptionOrNull(Parcel.java:3079)
    at android.os.Parcel.createException(Parcel.java:3063)
    at android.os.Parcel.readException(Parcel.java:3046)
    at android.os.Parcel.readException(Parcel.java:2988)
    at android.accounts.IAccountManager$Stub$Proxy.addAccountExplicitly(IAccountManager.java:1265)
    at android.accounts.AccountManager.addAccountExplicitly(AccountManager.java:1019)
    at com.owncloud.android.authentication.AuthenticatorActivity.createAccount(AuthenticatorActivity.java:1369)
    at com.owncloud.android.authentication.AuthenticatorActivity.onAuthenticatorTaskCallback(AuthenticatorActivity.java:1198)
    at com.owncloud.android.authentication.AuthenticatorAsyncTask.onPostExecute(AuthenticatorAsyncTask.kt:90)
    at com.owncloud.android.authentication.AuthenticatorAsyncTask.onPostExecute(AuthenticatorAsyncTask.kt:30)
    at android.os.AsyncTask.finish(AsyncTask.java:771)
    at android.os.AsyncTask.-$$Nest$mfinish(Unknown Source:0)
    at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:788)
    at android.os.Handler.dispatchMessage(Handler.java:111)
    at android.os.Looper.loopOnce(Looper.java:242)
    at android.os.Looper.loop(Looper.java:362)
    at android.app.ActivityThread.main(ActivityThread.java:8407)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:992)
Caused by: Exception in thread "main" android.os.RemoteException: Remote stack trace:
	at com.android.server.accounts.AccountManagerService.addAccountExplicitlyWithVisibility(AccountManagerService.java:495)
	at com.android.server.accounts.AccountManagerService.addAccountExplicitly(AccountManagerService.java:1707)
	at android.accounts.IAccountManager$Stub.onTransact(IAccountManager.java:565)
	at com.android.server.accounts.AccountManagerService.onTransact(AccountManagerService.java:1106)
	at android.os.Binder.execTransactInternal(Binder.java:1385)

    

    App information
    

      

    • ID: com.nextcloud.client
      • 

    • Version: 30310390
      • 

    • Build flavor: gplay
      • 

    

    Device information
    

      

    • Brand: motorola
      • 

    • Device: bangkk
      • 

    • Model: moto g84 5G
      • 

    • Id: U1TCS34.22-64-19-4-4
      • 

    • Product: bangkk_ge
      • 

    

    Firmware
    

      

    • SDK: 34
      • 

    • Release: 14
      • 

    • Incremental: c947fb-430a4c
      • 

  3. warthog9 commented on May 29, 2025 
    @warthog9
    warthog9
    on May 29, 2025
    Not to tag in but just noticed this on a Samsung S20+ 5G (Android 13, Google play system update April 1 2025, Android security patch level March 1 2025), Nextcloud app 3.31.3 (gplay) and last confirmed upload looks to be May 23rd (so 6 days ago).
  4. doits commented on May 30, 2025 
    @doits
    doits
    on May 30, 2025
    I can confirm it. Nextcloud android app update to 3.31.3 reset autoupload settings (happened on two pixel phones).
  5. lovwyr commented on May 31, 2025 
    @lovwyr
    lovwyr
    on May 31, 2025
    I can confirm it also, Pixel 8 Pro. Started with 3.31.3 directly on 28.05.
  6. DiegoRosales commented on May 31, 2025 
    @DiegoRosales
    DiegoRosales
    on May 31, 2025
    I can confirm. On a Motorola G73 started with version 3.31.3. I usually organize the pictures in different folders every few days, so now the auto-upload is re-uploading all pictures from my phone.
  7. dusatvoj commented on May 31, 2025 
    @dusatvoj
    dusatvoj
    on May 31, 2025
    Same on OnePlus Nord CE2. Few days ago there were probably update and now I can't fix the auto upload now. It doesn't correctly rescan media folders.
  8. meaglerick commented on Jun 2, 2025 
    @meaglerick
    meaglerick
    on Jun 2, 2025
    Experiencing the same issues on Nextcloud Android app version 3.31.3, Pixel 7 and Samsung Galaxy S21.
  9. K4r0qtuYNE5G4qgZ commented on Jun 2, 2025 
    @K4r0qtuYNE5G4qgZ
    K4r0qtuYNE5G4qgZ
    on Jun 2, 2025
    Confirm same Issue, just noticed on Pixel 9 Pro, Android 14, 512GB.
    
After Nextcloud Android App Update to 3.31.3 (came automatically) All Auto-Upload and 2-Way-Sync Settings were deleted.
    
After re-enabling Auto-Upload and Sync again, it tried to upload thousands of files and failed with Internet not available, but Internet was available. After kicking the App and restarting it, it suddenly had Internet again but thrown out thousands of popups "Select which one to keep" and then crashed. So I restarted it again and then manually canceled all Uploads and deleted all failed and set all Auto-Upload to "Skip Upload when already exist". I now hope this helps and also that it now work again.
  10. svenb1234 commented on Jun 2, 2025 
    @svenb1234
    svenb1234
    on Jun 2, 2025
    Any action on this regression? Maybe a notice in the release notes or pulling the release in order to avoid more users running into the problem?
  11. wookie73 commented on Jun 2, 2025 
    @wookie73
    wookie73
    on Jun 2, 2025
    I have had the same issue it started on the beta of 3.31.3
  12. daemongloom commented on Jun 3, 2025 
    @daemongloom
    daemongloom
    on Jun 3, 2025
    I have the same issue. Latest stable 3.31.3 from Google Play, Android 12, Samsung Galaxy S10.
    
It is the second issue in a short time when photo upload breaks completely without any messages/notifications to user and requires complete reconfiguration of upload settings.
  13. alperozturk96 commented on Jun 3, 2025 
    @alperozturk96
    alperozturk96
    on Jun 3, 2025
    Collaborator
    Hello everyone
    

    Unfortunately, due to a missing AutoMigration configuration in this release, updating to version 3.31.3 may result in the loss of folder configurations for auto-upload, two-way sync, and previously stored offline operations. This occurred because the Room database, without proper migration handling, was cleared during the upgrade process.
    

    We deeply regret this issue and understand how disruptive it can be. In response, we've released version 3.31.4, which includes a fix to prevent this from happening in the future. We’ve also implemented additional safeguards to ensure that similar issues are avoided going forward.
    

    3.31.4 is now available on GitHub
    

    F-Droid and Google Play Store updates are currently under review.
    

    If you are currently using version 3.31.3, please review and reconfigure your folder settings as needed.
    
In the meantime, we have released version 3.31.4 to ensure that users upgrading from 3.31.2 do not encounter the same issue.
    

    Thank you for your understanding and continued support. We truly appreciate the feedback and patience from the community as we work to improve the app.
  14. alperozturk96
    self-assigned this
    on Jun 3, 2025
  15. alperozturk96
    removed 
    0. Needs triage
     on Jun 3, 2025
  16. tobiasKaminsky commented on Jun 4, 2025 
    @tobiasKaminsky
    tobiasKaminsky
    on Jun 4, 2025
    Member
    3.31.4 is now available on Play Store.
  17. tobiasKaminsky
    closed this as completedon Jun 4, 2025
  18. regs01 commented on Jun 5, 2025 
    @regs01
    regs01
    on Jun 5, 2025
    

    3.31.4 is now available on Play Store.
    

    

    But not in F-Droid
  19. kbftech commented on Jun 17, 2025 
    @kbftech
    kbftech
    on Jun 17, 2025
    Hi,
    

    Configuration got reset on all devices we use. This caused a re-upload of every files into a default folder of each users (instantUpload) which cause an incredible load on the server and of course, tons of storage used for now duplicated documents.
    

    I'd like to know if there would be an easy way to crawl the folders of the users affected, compare the "instantUpload" folder to the desired folders and move the files which have been omitted for the past month or so, and delete the ones not needed.
    

    The main issue I see with this option is instantUpload is a flat folder (no subdirectories) so everything was uploaded without any ordering. The crawler would need to "build" the directory tree as it goes, as well as searching through subfolders to compare existing documents.
    

    The other option is to simply delete the "instantUpload" folder and have the users re-upload the files. This is easier said than done though because you can't "start" upload manually. It seems to start randomly for no apparent reason or at least I couldn't find how to trigger it. Then there is the bandwidth and server load but we can live with that.
    

    Any other suggestion?
  20. kbftech commented on Jun 17, 2025 
    @kbftech
    kbftech
    on Jun 17, 2025
    I just tried to trigger a re-upload from a client device and it just won't go. If we add a document, it gets upload in the right folder now, but existing documents are not checked (even though the option for "also upload existing files" is ticked).
    

    I think a "force sync now" button would be very useful.
  21. regs01 commented on Jun 17, 2025 
    @regs01
    regs01
    on Jun 17, 2025
    "also upload existing files" is non-recurring operation. Checkbox is indeed pointless, when it doesn't do anything. Instead it should be Reupload whole directory option in autoupload menu (menu with Hide folder and Configure) with confirmation of course.
  22. glaucon1984 commented on Sep 18, 2025 
    @glaucon1984
    glaucon1984
    on Sep 18, 2025
    Had to clear the queue of GBs of files being wrongly pushed to a local InstantUpload directory, filling the OS drive and killing my server, instead of the original mountpoint. It would freeze the auto-upload settings screen so I could not select the correct folder. After I managed to clear the queue I could reconfigure the correct folder but it no longer sees any "new" file pending for upload. I see the case closed but I fail to see how this issue is fixed or what the user can do to fix it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
Labels
bug
Type
No type
Projects
No projects
    Milestone
    No milestone
    Relationships
    None yet
    Development
    No branches or pull requests
    Issue actions