Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Dropbox no longer overwriting files
A few days ago, Dropbox stopped overwriting files when I edit and re-save them. Now, every time I edit one of my files on iPad and save to Dropbox, it creates a new file ending in (1). It used to sim...
I realize versions of this same question have been asked here before but I haven’t found any that satisfactorily address my frustration.
I want to begin by mentioning this is a NEW behavior for Dropbox. I have not changed anything I am doing, yet the outcome is now different.
I have maintained a spreadsheet (numbers version) on my iPad for years. Updating it & adding new information as it is available & with every update, I save it to my Dropbox. This has always resulted in the file within Dropbox being overwritten with the new version but it has never changed the name of the file. ie: adding a (1) or other sequential number behind the filename, until recently. In the other threads asking a similar question it was mentioned that this is expected behavior when saving a file from a different device. I want to emphasize that I am NOT saving from multiple devices. I am NOT doing anything differently (to my knowledge) than I have ever done when updating this/these spreadsheets. Again, appending the filename is a new behavior so something has either changed in the manner Dropbox is treating saved files or Apple made changes in their iOS that caused Dropbox to change the way it handles these saved files.
Can anyone offer help with this?
TYIA
JalapenoCheese , this is exactly what is being discussed here, so you are in the right place. I also save from only one location- my iPad. Previously, Dropbox would say that the file already exists, and ask if I want to overwrite it. I'd say yes, and be done. Now it does not prompt, it simply adds the new file with a (1) appended to the file name. I have to delete the original file, the rename the new one to get rid of the (1). This started after a Dropbox app update a while back, and has happened before- I think I linked my report of the prior occurrence in this thread. It sounds like so far there has just been lots of runaround.
