There is a button titled “Create date.txt”. And “file.ext” won’t exist locally!ĭetails - my test app defines a file named date.txt in the ubiquity container (dateFileURL). It won’t the new will get named “file 2.ext”. Tl dr - this happens when an existing “file.ext” exists in the iCloud account but hasn’t been loaded to a new/second device, and then the new device creates (another) “file.ext”, thinking it’ll overwrite the one in the cloud. I found the same thing, and wrote a test app to investigate. Seems I was able to find one more instance of someone else experiencing this-unfortunately, the solution was the same as what I described above. DUPLICACY ICLOUD UPDATEUpdate 31 August, 2016: Unfortunately, it seems that fix was only temporary, and the behavior reverted. It would do a fresh sync with iCloud Drive and then behave properly. The solution was to move the file out of iCloud Drive (e.g., the Desktop folder), confirm to iCloud that the file was “deleted,” and then move the file back. Finder would then see that the file with that name already existed and then append a number to the name to distinguish from the original. It appeared that iCloud was syncing it up to iCloud Drive, thinking that a local copy didn’t exist, and then bringing back down the saved copy. In other words, if the file was originally called When Harry Met Sally, saving would then produce another file called When Harry Met Sally 2. One of our users ran into an issue with saving a file and then suddenly (or shortly afterward) having the same file (with a 2 or 3 appended to its name) appear. This is kind of a bizarre scenario, but I thought I’d document it, in case anyone else runs into a similar issue, since I wasn’t able to find it through a Google search.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |