Thanks KB. I appreciate you sending the S over here to hang out with me and my memories of K… It was getting a bit lonely over here.
Tell the son that being in the corner is where all the cool kids land before they learn how to fit in. I appreciate his company too 
This one was the daughter - the son is now taller than me. 
Aaaand I’ve pulled the update again until tomorrow after it has transpired that Scrivener crashes on the macOS 11.1 beta. I’ll have it fixed up tomorrow. This is turning into a fun release!
Why is it in the corner, indeed.
Crashes get trashes?
Isn’t software development never-ending fun?! Thank Heaven I’m retired now…
My reaction regarding the icon: “Oh. The iOS icon. It’s arrived.”
As I don’t use the iOS version, I’d never seen the icon before but I have to say, I do like it.
Right, we’re back up again - for the last time I hope!
Perhaps this is utterly unrelated, but I upgraded to 3.2 in the last hour (since KB’s post above), and have experienced two crashes since. Prior to that I can’t recall the last time Scrivener crashed on me. Have submitted two reports using the automated crash reporter, hope they’re helpful.
The crashes you experienced should now be fixed in 3.2.1 - thanks for sending the reports.
Same! I upgraded to 3.2 yesterday, and now I cannot open my project 
. I updated my Macbook Pro to Big Sur today, and it still crashed. I hope this issue will be resolved soon.
Great, thanks very much KB.
See the post directly above yours, and upgrade to 3.2.1 if you haven’t already
Scrivener has crashed on close several times for me. And now my current WIP won’t open…crashes Scrivener every time. I opened a backup and duplicated it with a new name…make the SAME changes a second time. And now that file will not open either without crashing the program. HELP! I don’t have time to continue making the same changes over and over again.
I upgraded yesterday, which was the last time I worked on the file until today.
3.2 and 3.2.1 sometimes crashes on exiting a document or the app for me too. I’m on Big Sur. I sent the automatically generated reports. Fortunately no documents are corrupted. All my projects are plain text with no formatting, if that helps.
For crashes tied to a single project, the first thing to try is resetting the project’s display settings as explained here:
scrivener.tenderapp.com/help/kb … y-settings
If that doesn’t help, please open a support ticket. Include a copy of the crash report, and mention that you’ve already tried resetting the project. (Otherwise we’ll suggest you do so as a first step.)
literatureandlatte.com/contact-us
Katherine
I can’t reset anything since I cannot open the file. It crashes. I have to go to an older one.
The link I posted includes instructions to follow if you can’t open the project.
Katherine
I’ve been struggling with instacrashes as well. It started after I updated Scrivener on Mac (still running Mojave), then tried to open a huge .scriv file that I’ve been working in for years.
Scrivener crashed, offered to let me send a crash report, and then asked me to reload. I was able to get Scrivener to open without a project by holding down shift when I clicked on the app in the Dock. But no amount of troubleshooting tips (I tried this: scrivener.tenderapp.com/help/kb … y-settings) seemed to work.
I was desperate to get my project back, so I created a blank project and tried importing the old file. It seemed to work, but then I saved the new project and closed it. When I tried to reopen the new project again: crash.
At that point, it seemed pretty clear that there was some setting or object being imported that the new release of Scrivener could no longer handle opening. I couldn’t tell what it was at first; I have everything from linked webpages to images in my project.
So I imported the old original project again, this time selectively deleting files so that only a few documents were saved in each version of the project. Ultimately, I was able to narrow down the culprit:
I have no idea what the italics are doing. They’re not italics copied over with rich text from some external document; it was literally just me hitting cmd+i within Scrivener.
Anyway, for several hours last night, I thought I’d lost years of work, as the Scrivener backup was crashing similarly. I can’t afford to lose any work, so I guess I’ll be switching to MS Word until Scrivener has a fix for this. Would love to know if I’m the only one experiencing this.
Since you’ve narrowed it down to one document, have you sent a project containing just that document to Scrivener tech support?