Ok, its possible the crash is unrelated. Maybe something is in the console logs I posted in regards to the freeze?

Is there a way to run the Filebot.app with logging to a file or the console? Not sure how to do it from the terminal..

Here is the stack trace for attempting to open the folder by dragging to filter.
https://pastebin.com/UxdREGuk

The console logs (not all but enough see the sandbox issues) for when The permissions popup shows:
https://pastebin.com/eiw0706N

This issue is still happening for me and it’s the worst. It pretty much makes Filebot unusable for me. Unfortunately I don't have another machine I can test with, but mind you I've upgraded my system through at least two major releases of MacOS since I reported this issue and the issue still happens. ...

That worked. Thanks!

@rednoah Can I please receive a complimentary license for Filebot-CLI? I had previously purchased on Mac App Store.

I am running Filebot via the command line. I had previously purchased the Mac App Store version and in the Mac version I had some presets. When loading filebot from the command line though (installed via brew cask install filebot) Filebot can't find my presets. Where are they located? I tried ...

Under the yearly license does Filebot keep working completely featured? Then its your option to pay to upgrade only?

You could try to preemptively drop in the destination folder before processing any files (e.g. into the Filter panel) and then try again. Dropping files into FileBot should make the OS give FileBot access, and then it shouldn't need to ask for access later, skipping the bit where Finder freezes ...

Yes it hangs as soon Filebot opens Finder to the root directory where the folder it wants permissions is in. Right then and there the beachball happens. I tried all other conditions you mentioned.. with the source file being on the local drive, and from an SMB share and the results are the same ...

The suggestions provided above dont work for me because the beachball comes up and Filebot stops responding and must be forced-closed. Loading the entire folder doesn’t truly work for me as it seems Filebot is trying to gain access to the destination folder and not a folder I can "load" as a source. ...

I am getting this issue as soon as the Folder Permissions Required Window pops up on Filebot. What can be done as this really really annoying?

When I attempted to do the upgrade through the Mac App Store the initial update failed. And then after attempting later it worked. Maybe its possible the App store removed the application and reinstalled it?

So I upgraded Filebot to 4.8 via the Mac App Store and now my presets are gone. I am on High Sierra 10.13.4 (17E199). Where are they usually stored on OS X? I do backups so its possible I can restore them but they definitely should not have been deleted in the first place.