Actually, in the meantime. Sadly not a mac person in any way but I did Google very fast and then saw something about a code signing issue. Wonder if it is maybe an issue with the latest version.
@ivov had a look. And he identified that the tunnel service with an expired SSL certificate is probably the issue. I just fixed that issue. Can you please now try again and see if it works. Thanks!
n8n will by default try to connect to our tunnel service as without it most trigger nodes will not work. It should be possible to change that. @ivov should know more about that.
No, if you run n8n locally via npx or Docker then it will not be a problem as you can then easily choose if you want to start with tunnel or not.
Thanks a lot for the offer! But the thing that we do not have enough of at n8n is not money, it is developer resources. For that reason do we not focus on things that will pay us money now, we rather focus on things that will improve the product most, will help our users most and will make n8n most successful in the long term. That said, as @ivov pointed out should not be too hard to do. Maybe we can sneak it in with the next n8n Desktop release.