Yes, this is a “standard response”, given that our standard response to users’ technical issues is to try to help them resolve them as best as we can, which is what I had hoped to do here. As part of that, I explained how the file system works, and how Scrivener’s access to it is all handled by OS X. Even though this is not likely to be a Scrivener issue, I most certainly did not say “tough on you” - in fact, I asked you several questions so that I could get more information in order to try to help you. As I said in my previous reply, the issue is trying to pinpoint what it is on your machine causing the problem, because this is not a general problem with Scrivener - we would be receiving hundreds of complaints about this if it were. If it turns out to be a Scrivener issue, you can rest assured that I will do everything in my power to fix it. Just take a look at the change list on our product page or my responses to bug reports on these forums - you will see that my “standard response” is to do everything I can to ensure Scrivener is as stable as possible and bug-free. Scrivener has a reputation for being stable, and I do my utmost to maintain that.
If I say that I think an issue is not likely to be caused by Scrivener, I don’t say this lightly; I say it from experience and from my knowledge of the code (I am the programmer). And even when something is not likely to be a problem with Scrivener, we still do our best to help users track the exact cause and resolve things. So if you are interested in getting some help rather than assuming the worst about us or Scrivener, then please read on…
First, you didn’t answer whether you have any anti-virus or security software installed - do you? This makes a difference. If you do, what software is it? For instance, ESET CyberSecurity is known to cause problems.
The next thing to do is to establish is whether this is indeed a Mac App Store sandboxing problem. To establish that, move Scrivener to the Trash and download the non-sandboxed version from our website:
literatureandlatte.com/scriv … atform=mac
Install that version. As long as you have run the Mac App Store version once, as you have, the version on our site recognises you as a registered user, so you are free to use it.
Please let me know whether the direct-download version has the same problems. If it does, then it’s most likely something else on your computer interfering, and we have to look into what that is. If the direct-download version works fine, then this suggests that the problem is caused by the sandboxing security features that the Mac App Store insists upon. Even then, this shouldn’t happen, and it suggests a clash with some third-party software that you are running - which, again,is why it’s important that I know if you do have any security software installed.
If not, do you have any other plugins installed?