Well, I don’t know if there is that severe a misunderstanding—if what 2albion means by getting it over to the computer is using one of the methods I described a couple of posts back, to get the working copy off of the iPad without Dropbox, then yes what they describe makes good sense and is exactly what I would recommend in this scenario:
- You send a copy from the iPad to the Mac somehow (AirDrop, iTunes Wifi, USB cable, third-party file manager, whatever).
- You try to open the project fresh off of the iPad on the Mac.
This procedure avoids any potential complications that may arise from Dropbox usage, it is the cleanest and simplest way to work in fact, in that it involves no external complexity. So if a project does not open after copying it directly off of the iPad—that indicates there is a problem with the project, not the process (though naturally processes in the past might ultimately be the culprit in the project’s current state—we at least eliminate process as a present-tense factor, which is valuable).
I’d need a little more information than that, to provide any further advice, sorry. It works best to describe all of the error messages you get, the things you see happening on the screen, etc.
One thing I would suggest regardless of the symptoms is to right-click on the project in Finder and “Show package contents”. You should see these folders: Files, Settings and Mobile (there may be more but they are not crucial). You should see one, and only one, .scrivx file. If you see missing folders or many conflict copies of the .scrivx file, then this project needs repair, and is only opening on iOS out of fortune.
Lastly, when you say this happened again, I think that’s a good sign that you should carefully evaluate your procedures—take notes on the actions you take for a while, both in how you use the software and how you sync. This is not a normal cause and effect you’ve encountered. Projects do not typically spontaneously stop working. If it happens once, then maybe something very unfortunate happened like a bad transmission over Dropbox. But if it happens twice? Well, I’d start looking in to what I’m doing at that point, and simplifying my procedure over time as much as I can, noting what seems to work better and what doesnt.
And if you are coming up against a bug, these notes will be valuable in communicating to others how to find it, too.