Sorry. The replies came in to my email in the wrong order. I just saw your explanation now. I've tried this on two versions of 10.15.6 running Yate v126.96.36.199. It works as expected. I'm assuming that this is not a generic issue as I'd certainly have heard and I have not had any other reports on this.
While I can crash Catalina at any time by opening the File Save panel in a particular way I've yet to see any issues with the File Open panels ... other than very rarely they simply do not open. I've seen this in a number of application. Yate handles this case by simply returning and doing nothing.
Just to make sure here are the steps:
- you do a File>Open
- the open panel is displayed
- Yate should not be responsive when the panel is displayed. Clicking anywhere in Yate should cause a beep. However, there should definitely not be a beachball as Yate is being blocked by the Open Panel.
- after a few minutes, the 'finder' panel closes on it own. Yate never does this. As I said the Open Panel is being run by Apple in a different process and Yate is completely blocked.
Something here is corrupted as it seems as if the OS is not properly handling Yate's request to process the file open panel.
Just for fun do a Yate>Import Preferences. This also displays an open panel in exactly the same manner. Different code but exactly the same approach.
Something is going on external to Yate if you upgraded last week and the issue just started yesterday. There is no reason that the code should stop working after a few days. The code is static and does not change.
It's entirely possible that something has been corrupted on your system. The first thing I suggest doing is downloading Yate again from the web site and installing it over your existing version. That will fix Yate if the binary has somehow been corrupted and you will not lose any of your settings. Regardless as to whether that works or not I suggest checking the drive as there might be corruption there. You can do this is Disk Utility. Let see what happens with one or both of these steps (and the File>Import test). In the worst case you might have to try reinstalling the OS (not a clean install) in order to restore whatever is messed up.