When I create a new document in the iOS version, and then go back and sync to the computer it always goes into a “Recovered Files” folder and erases the title that I named the document. The first time this happened I thought it was just me, but it has now happened several times, and I don’t think I’m doing anything outside of syncing protocol. This only happens when I create the document in the iOS version.
I am not sure if this is with the project remaining open on the computer or me opening it fresh on the computer. I’m fairly certain I’ve had it happen with both scenarios, but I will check.
If you have a project open on the computer while opening, editing and saving it on the iDevice, I can almost guarantee that you will have problems and will get conflicts/recovered files.
But you wrote that it happened with new projects, created on the iDevice? In that case the project can’t have been open on the desktop, right? So how did you open the project the first time on your computer, after having created it on the iDevice?
It is also the case that when you hit sync in iOS scriv when you are done with the project, you have to stay there until the sync finishes (it will not complete in the background or during device sleep).
I tried to reproduce the phenomenon reported, but have not succeeded.
No, no. When I create a new document inside a project, not a new project. That’s when I have the issues.
As to the bolded part, isn’t it supposed to work with the project still open? That’s what the blog said, I’m fairly sure. I’m still very much waiting for Dropbox to sync up before going back to Scrivener in the computer and having it sync then.
“You are free to leave the project open on your Mac or Windows machine while you use and edit it on iOS. After you sync, the changes will be detected and incorporated into the project.” literatureandlatte.com/blog/?p=713
Thus, it should work how I am doing it. The only difference is that I’m leaving it open where you have it as being closed, and the blog says you can do that. Everything else I am doing is exactly the same. Even if it does work under the circumstances you outlined above (I realize this is probably the more “conventional” way to do it) it’s still not acting right under the circumstances I am using, and it is supposed to by Lit&Lat’s account.
Leaving it open on the Mac side should work if everything syncs before you move from one device to the other. I tested that during the beta myself (as did many other people, I’m sure).
There should be a “mobile sync” button in your Mac Scrivener toolbar (you can add it if you don’t see one). If you click it after creating a document using the iOS version (and after syncing), does that alleviate the problem? If it doesn’t, then you should contact the support email directly. They’ll probably want to see a copy of the project to see if there’s something messed up in the inner workings of the project file.
I’ve been waiting until Scrivener actually alerts me by itself that there were changes made to the mobile version even if Dropbox is done syncing, since it automatically detects changes. I don’t want to interrupt its process.
That’s what I’m starting to wonder. It’s a big file, and (if I remember right) it only started doing it after a few syncs.
You also might want to “reveal contents” of the project file (right-click in the finder) and search for files with “conflicted” in their names within the project’s contents. If that’s the case, they can help you sort out which of the files to keep, and which ones you can remove from the project.
I actually don’t have issues with conflicted documents, at least beyond my own fault. The new documents that I create in the iOS version come up as “Recovered Files” on the computer, go into a separate folder, and the title gets replaced. That’s what I’m having trouble with.
And what kind of iOS device? “Recovered files” sounds like they weren’t saved properly, with all meta data, so I just thought that maybe there could be a memory issue on the iDevice?
Forgotten Gold, do you have External Folder Sync enabled in your project? This is NOT intended to be used with iOS Scrivener, and can lead to the recovered files error.