Compiled outputs don't show up in Finder

I am having a new problem with compiled files (after some problems compiling a corrupted file that is now fixed). I haven’t ever had this problem before, with any outputs.
When I compile to different outputs (I’ve tried .docx, PDF, and epub) the file is not visible where I’ve saved it. For instance, I have tried to save it to my Desktop, but it does not appear.
However, the file is always there, just hidden. With docx files, if I search for the filename in the Finder, it shows up in the results. Even weirder, suddenly the files appear on my desktop.
For epub, if I select “Open…” in Preview, I can see the epub file sitting there, but can’t select it. In iBooks, for some reason, the “Open” command is greyed out, so I can’t see if it shows up there. But the ebook itself opens automatically in iBooks. I just can’t see the file itself either in the Finder or on my desktop itself.
I tried saving to a different file location, and the same thing happens.
I worked around the docx problem by searching for the file, but I can’t figure out how to access the epub, which is a problem.
Is there a way to get the files to show up when I compile? I am at a bit of a loss.
Thanks for the help.

Hi.
I am a Windows user. So I can’t help much with the filter your computer is likely using as to what file types are hidden by default. (Could be a permission thing too. Are you running your computer as Administrator? – If there is such a thing on a Mac.)

But but but, I’m here to tell you that if you want the file to open automatically after a compile, check this option in the compile panel:
image
:wink:
It is not a solution, I know, but it is already better than nothing.

What version of Mac OS do you have?

This is not really something that Scrivener can control. Any location that Scrivener is allowed to write to – which these definitely are if the file exists – should be accessible to the user. If it’s not, then Mac OS is doing something unexpected.

thank you for the reply. I thought the problem started after the latest compile, but my husband did some investigation and it had actually started a while ago–meaning it’s not related to Scrivener. Sorry for the false rabbit trail!