question Is the need to notarize a DMG really a hard Apple limitation for distributing Mac Apps beyond your local build machine What makes me doubtful is that you frequently come across ad hoc distributed Mac Apps in the wild which refuse to run normally due to having not being signed and yet <https www howtogeek com 205393 gatekeeper 101 why your mac only allows apple approved software by default ~ text=To 20open 20an 20unsigned 20app with 20a 20valid 20developer 20signature |you can still run them> with Right Click gt Open on the App as a kind of confirmation that you accept the risk What makes CfD s packaging different Could we not achieve the same experience It s not ideal of course but still very useful in many situations e g just wanting to share a utility App with colleagues

❓ Is the need to notarize a DMG really a hard 'Apple' limitation for distributing Mac Apps beyond your local build machine? What makes me doubtful is that you frequently come across ad-hoc distributed Mac Apps in the wild; which refuse to run normally due to having not being signed; and yet you can still run them with 'Right Click -> Open' on the App, as a kind of 'confirmation' that you accept the risk. What makes CfD's packaging different? Could we not achieve the same experience? It's not ideal of course, but still very useful in many situations e.g. just wanting to share a utility App with colleagues.

ephemient

04/06/2022, 8:08 AM

macos is getting stricter. unsigned M1 apps won't even run with right-click.

Michael Paus

04/06/2022, 11:03 AM

The strictness also depends on the version of your macOS and how you download the file.

Kebbin

04/07/2022, 12:38 AM

Interesting! Even for people testing my program in macOS, it looks like I'll have to try just JVM jars.

3 Views

#compose-desktop Join Slack