Welcome aboard! While I don’t know Macs at all, in the github issues section there is a report from someone running Fritzing 0.9.4 on Mac OS 10.15. I’d probably suggest opening an issue on github here:
if no one has a suggestion here. You also may want to try 0.9.3b (assuming you are currently on 0.9.4 which is the latest release) to see if that works.
I see the latest version has a couple of MacOS names (no version numbers), is 10.5 older perhaps? The new release is using an entirely new tool chain (as the one used for 0.9.3b in 2016 no longer exists.) It is possible they didn’t (or couldn’t) support older Mac versions, but I don’t really know. Probably your best bet would be to open an issue on github and ask if they do support MacOs 10.5 on 0.9.4 or may add it in a future release. As I said I am not familiar with MacOS, so I don’t know what is involved or thought to be supported now.
Then as far as I know 0.9.4 should work as well as 0.9.3b. I’d suggest reporting this as an issue on github so it gets tracked and hopefully addressed. The folks that make the releases do sometimes read the forums, but they should get notified by email of an issue opened on github. I expect they would appreciate any error message that comes up when 0.9.4 doesn’t run as well. Sorry I can’t be more help .
Well, I’m using Fritzing 0.9.4 under Mac OS Catalina 10.15.4 with very few problems - mostly of my own making!
i.e managed to duplicate a part but still had the same id so an error occurred - easily fixed !
Also trying to add a strip board for prototyping with more rows and/or columns than the standard set size seem to provoke a memory attack of the rainbow spinning ball and it slows to a snails pace.
So what actually happens on your machine after a double click - something must happen albeit that it launches and quits immediately with no warning. Almost sounds like a corrupt support file - plist or similar. Maybe a complete deinstall using an app such as ‘ApplCleaner’ (free of course) to make sure all remnants of the old version are removed and then a clean install again might help!
PLEASE - make a backup of parts database and your own first!
I’ve had this happen many times when upgrading various applications and its nearly always been corrupt support files. I use the app cleaner method because it can find associated files which may not have the app name in it - developers get up to all sorts of tricks sometimes to protect their app.
Also Apple have changed so many permissions for security in the latest OS which may have contributed to the issue!