I had over 100 crash reports pertaining to Scrivener crashing on close or backup. It seems this was all down to a single stray setting in one of the .nib files. I have just uploaded a revised build of 2.0 (build 6023). Please re-downloading Scrivener from the main page, ensuring that you clear your browser cache before you do so.
Once downloaded and installed, ensure that it says “2.0 (6023)” at the bottom of the Scrivener > About Scrivener panel.
This should, I hope, fix the crash-on-close-or-backup bug.
I am working on all the other bugs and crashes reported so far as fast as I can.
Might as well; since you can keep the preference files, it’s absolutely painless. Download the new one, trash the old one from Applications, put in the new one. Done. You won’t even lose project names from the “recent projects” list. I wasn’t having the crash problem, but I upgraded for the sake of upgrading. You never know when a lurking bug will suddenly bite you.
I hate exposing myself as an idiot (although it probably is no secret by now), but what is a browser cache and how does one clear it? I’m using Safari, if it matters.
Thanks for your help, all of you who make these forums so infinitely useful.
The cache is basically where the browser stores copies of/parts of the webpages you visit, so as to cut load time when you revisit the same site. (Okay, that’s really simplified, but the point is there.) Some people experienced a problem the other day when trying to download the new 2.0 version where the browser wasn’t giving them the proper page and the right download, so they were basically getting the old version that was cached in the browser. Chrome particularly seemed to have this issue. I didn’t have any trouble with Firefox just now. Anyway, to be safe, you can just use Safari>Empty Cache… and then load the Scrivener page and get the newest download.
Thanks; I cleared the Safari cache and downloaded S2. The back-up problem I had had on one project (a total refusal to click on iDisk at all) disappeared. Hopefully a small plethora of other problems will be gone as well.
Unfortunately, neither of them is the latest 2.0 (6023) version. Is there any way for you to get amazonaws.com to refresh their cache and pick up your latest changes?
That did it! Yea! Thanks! Please ignore the half dozen crash reports I have sent tonight. (I kept hitting the do not send button and it sends anyway. Would that be a metabug?)
I knew there would be a report here but I couldn’t get in! For the past three hours I have been getting only 503 errors from the forum.
%$#@ it Keith! Your stuff is too popular! You need cloud servers like NaNoWriMo does.
Again… thank you so much for the rush job on this bug fix. This one was driving me nuts because it crashed randomly for me and I LOVE my zip back up.
Thanks for the fast update. My new copy says “2.0 (6076)” – this is even newer? And wouldn’t it be helpful to have this in the Get Info box so you can find out without actually running the app?
And no, it would not be right to have the build number in the Get Info box, that’s not customary - normally you wouldn’t need to check the build number as I would be pushing out 2.0.1 updates, but I’m uploading as I fix things and will bundle all into a 2.0.1 update soon.
Okay then. Thanks for the reply. And thanks for the bug fixes, the upgrade, the app itself – oh, heck, thanks for just everything about Scrivener, the little app MSWord only wishes it could be (Ha! In your dreams, Mr. Gates!)
Question: does check updates in Scrivener not automatically download the new builds? If not is there a preference setting that would allow me to always have the latest update?
These builds aren’t going out as automatic updates just yet. I don’t want to bug all users with automatic updates every day - instead, I’m working through all the main fixes, updating the version of Scrivener on the site as I do so, then everything will be rolled into a 2.0.1 update in a couple of weeks that will go out through automatic updates. Everyone who sends me an automatic crash report receives an e-mail telling them to download the updated build, so I’m trying to ensure everybody is using a stable version, but I want to clear all the main issues before sending out 2.0.1.
Hope that makes sense!
All the best,
Keith
I wasn’t having the crash problem, but I upgraded for the sake of upgrading. You never know when a lurking bug will suddenly bite you.