You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
over the last couple of months we enhanced our auto upload system and tried to make it more reliable and bullet proof.
But we also learned and see from your reports and comments that it is still not in perfect shape.
Thus we ask you to contribute if you experience a problem with auto upload.
How you can do this?
We will provide you with a drop in replacement for current stable Play Store version. It is a APK file, signed with the same release key that we use for releases on Play Store.
It is hosted on our cloud.nextcloud.com, so you can be sure that it a trusted source.
Since it is a drop in replacement every app setting will remain and even new updates via Play Store will work.
we will analyze your problem and logs and try to solve the issue
it might be that we then hand out a new version to you, which you can install again, so we can iterate on it together and eventually will solve the problem
Why I cannot use F-Droid?
F-Droid doesn’t distribute the exact APK that the original developer publishes. Instead, the F-Droid project builds the app itself from source code and then signs it.
Thank you for your help!
Nextcloud Android Team
Changelogs
APK (2026-02-23): Fixes auto-upload job cancellation issue and worker policy
RC 33.0.1 (2026-03-12): Fixes auto-upload work policy, duplicated db-entries, file system entries insert
Please enable the possibility to export logs also in the regular playstore-version of the app (as it seems, this is currently not possible, at least i don't see a settings-entry for logs). not everyone can (or should) enable 3rd-party APKs to test this. especially not on e.G. company-managed devices, or when you use banking-apps, that may require this (or require the device not beeing rooted). there would be absolutely no downside to have the possibility to generate logs from the regular app, too.
I downloaded the App. I opened the APK. My Pixel 7Pro says, it want's to scan it. Scan says: Clear to go. I pushed "install". The phone works a bit, then says: NOT INSTALLED. 🤷♂️ My current version is 3.35.2 from F-Droid. What's next?
On Pixels you likely can't update to a version signed by different certificate. Stick with F-Droid.
Please enable the possibility to export logs also in the regular playstore-version of the app (as it seems, this is currently not possible, at least i don't see a settings-entry for logs). not everyone can (or should) enable 3rd-party APKs to test this. especially not on e.G. company-managed devices, or when you use banking-apps, that may require this (or require the device not beeing rooted). there would be absolutely no downside to have the possibility to generate logs from the regular app, too.
The above APK is a special build with more logs than we want to have in a regular release.
With normal releases we additionally do not store any logs, since the less we store, the less could be leaked or retrieved by an attacker/malicous app.
This is build is no 3rd party app! It is signed with exact the same signing key like our official releases, thus making it a drop in replacement.
But you are right, on company managed devices this might not be possible.
Rooted device is not needed.
@jamfx for Fdroid we cannot offer such a drop-in replacement since Fdroid builds and signs the release with their key.
If you want to help, I fear the only way is to uninstall Fdroid published app and install (and reconfigure) above APK.
Reacted by JamFX, Sanookmakmak and Daniel Scharmach
I don't want drop in replacement. I would like to install yet another version (it could be the Play one) with separate test Nextcloud account. But I get:
Do you want to update this app?
Update
App not installed as package conflicts with an existing package.
Edit
There is F-Droid Dev version which has logs and installs as a separate app.
Before NextCloud I used pCloud. While there were reasons why I stopped using them as my main cloud, they got 1 thing right: when you created an account on your phone, it created a DB of all images and videos that it already uploaded. Sure, it would lose the db after reinstall, but as long as you did not reinstall the app, there was a file tracking what was uploaded and what hasn't yet.
At the cost of, IDK, a few dozen MB I was certain that I won't lose several hundred/thousand MB of data. Why not go for that design if the current one (listening to events I guess?) after several iterations still fails? Today I plugged my girlfriends phone and run my script that looks for not uploaded images and videos (and uploads them) - since the last time I've run it there were 1200 files/16GB of not backed up data! I really would not mind some uploaded_files.db there (even if it took several hundred MB) if I didn't have to constantly worry that if I won't run my AI-generated slop script, my data can be lost because the android app skipped an event.
I'm sorry if I sound harsh, that's not my intent, but I am frustrated that something so important still does not work, and it could be made bulletproof by design (1 DB file in the app's own folder with list of uploaded files, access to camera folder files' listing, compare the 2 on event OR every once in a while, perhaps trace some last modification date to skip comparison if nothing was added, remove files that got removed, etc). I'm sure there would be some unexpected issues, BUT if one traced which files were uploaded, then it would still be possible to deploy a bugfix which would re-compare the lists and found out missed files.
Reacted by dataprolet, PAFriedrichMueller, svenb1234, Otto Sabart, vitrex and Ely Deckers
Yeah after I first encountered this issue after the auto upload overhaul, I rolled back to 3.34.1 (from November 2025 if I am correct). I'm currently overhauling my server to run on fedora coreos and I'm seriously considering dropping nextcloud after 8 years, on this new build. I need a functional android app to use this service. And not one that's nearly a year out of date.
To help keep the discussions organized and ensure the main topic, I created separate referenced issues for some of the comments and marked the corresponding older comments as outdated, fyi.
Activity
zeus86 commentedon Feb 19, 2026
Please enable the possibility to export logs also in the regular playstore-version of the app (as it seems, this is currently not possible, at least i don't see a settings-entry for logs). not everyone can (or should) enable 3rd-party APKs to test this. especially not on e.G. company-managed devices, or when you use banking-apps, that may require this (or require the device not beeing rooted). there would be absolutely no downside to have the possibility to generate logs from the regular app, too.
jamfx commentedon Feb 19, 2026
regs01 commentedon Feb 19, 2026
On Pixels you likely can't update to a version signed by different certificate. Stick with F-Droid.
jamfx commentedon Feb 19, 2026
tobiasKaminsky commentedon Feb 19, 2026
The above APK is a special build with more logs than we want to have in a regular release.
With normal releases we additionally do not store any logs, since the less we store, the less could be leaked or retrieved by an attacker/malicous app.
This is build is no 3rd party app! It is signed with exact the same signing key like our official releases, thus making it a drop in replacement.
But you are right, on company managed devices this might not be possible.
Rooted device is not needed.
tobiasKaminsky commentedon Feb 19, 2026
@jamfx for Fdroid we cannot offer such a drop-in replacement since Fdroid builds and signs the release with their key.
If you want to help, I fear the only way is to uninstall Fdroid published app and install (and reconfigure) above APK.
jamfx commentedon Feb 19, 2026
zeus86 commentedon Feb 19, 2026
zc-devs commentedon Feb 19, 2026
I also have F-Droid version.
I don't want drop in replacement. I would like to install yet another version (it could be the Play one) with separate test Nextcloud account. But I get:
Edit
There is F-Droid Dev version which has logs and installs as a separate app.
regs01 commentedon Feb 23, 2026
alperozturk96 commentedon Mar 4, 2026
59 remaining items
MateuszKubuszok commentedon Jul 23, 2026
Before NextCloud I used pCloud. While there were reasons why I stopped using them as my main cloud, they got 1 thing right: when you created an account on your phone, it created a DB of all images and videos that it already uploaded. Sure, it would lose the db after reinstall, but as long as you did not reinstall the app, there was a file tracking what was uploaded and what hasn't yet.
At the cost of, IDK, a few dozen MB I was certain that I won't lose several hundred/thousand MB of data. Why not go for that design if the current one (listening to events I guess?) after several iterations still fails? Today I plugged my girlfriends phone and run my script that looks for not uploaded images and videos (and uploads them) - since the last time I've run it there were 1200 files/16GB of not backed up data! I really would not mind some
uploaded_files.dbthere (even if it took several hundred MB) if I didn't have to constantly worry that if I won't run my AI-generated slop script, my data can be lost because the android app skipped an event.I'm sorry if I sound harsh, that's not my intent, but I am frustrated that something so important still does not work, and it could be made bulletproof by design (1 DB file in the app's own folder with list of uploaded files, access to camera folder files' listing, compare the 2 on event OR every once in a while, perhaps trace some last modification date to skip comparison if nothing was added, remove files that got removed, etc). I'm sure there would be some unexpected issues, BUT if one traced which files were uploaded, then it would still be possible to deploy a bugfix which would re-compare the lists and found out missed files.
Ronkn commentedon Jul 24, 2026
Yeah after I first encountered this issue after the auto upload overhaul, I rolled back to 3.34.1 (from November 2025 if I am correct). I'm currently overhauling my server to run on fedora coreos and I'm seriously considering dropping nextcloud after 8 years, on this new build. I need a functional android app to use this service. And not one that's nearly a year out of date.
dataprolet commentedon Jul 24, 2026
svenb1234 commentedon Jul 25, 2026
schneidr commentedon Aug 9, 2026
tristanbay commentedon Sep 3, 2026
alperozturk96 commentedon Sep 7, 2026
Hi,
To help keep the discussions organized and ensure the main topic, I created separate referenced issues for some of the comments and marked the corresponding older comments as outdated, fyi.
34.1.1 replacement APK shared: https://cloud.nextcloud.com/s/7PqWpANQQqMPXpk:
Thanks.