melonDS is not notarised on macOS

[ketsuban]

Versions of macOS prior to Sequoia allowed running unnotarised code by rightclicking (Control-clicking, two-finger-clicking) the bundle in Finder and choosing "Open", but malware started instructing users to do this. As such, macOS Sequoia removed this process and instead requires you to attempt to run the software in question, open System Settings and in the Privacy & Security pane manually whitelist the software (which also requires typing your user password).

melonDS is signed only with an ad-hoc signature and not notarised, so it falls foul of this change. The problem was reported in #1257, but that issue suffered from a case of the blind leading the blind and was "resolved" by the user taking the above series of actions without explanation (hence the forlorn comment a year after the issue was closed asking what they did). The correct resolution is for Arisotura to incorporate notarisation into the process of creating the .dmg file containing a melonDS bundle.

[nadiaholmquist]

Probably won't happen. Getting access to a developer certificate usable fur notarization requires a recurring yearly payment and I doubt there's much interest in having to pay that.

[ketsuban]

You don't have to pay for notarisation on a per-app basis, as long as there's someone willing to use their credentials to have melonDS notarised. (I know Arisotura has interacted with Vicky Pfau, for example, and mGBA is already notarised.) The only downside is that both tools are affected if the signing certificate is later revoked for any reason.