I believe that DropDMG just signs the installer and does not sign the app. You might take a look at AppWrapper3 or dive into Trevor’s Levure framework - it works with DropDMG to sign both the app and the disk image.
Marty > On Dec 29, 2018, at 12:20 PM, Peter Bogdanoff via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hi, > > I’m using DropDMG to sign my macOS installer. Users are having trouble > opening it—Gatekeeper seems to not recognize my developer ID. > > It is unclear to me what is going on. Does the application need to be signed > before I create the installer in DropDMG? And how do I do that? I had thought > that DropDMG took care of everything… Michael Tsai says "The app should > definitely be signed before creating the .dmg.” > > https://c-command.com/forums/showthread.php/4103-Signing-app-to-prevent-Gatekeeper-block > > <https://c-command.com/forums/showthread.php/4103-Signing-app-to-prevent-Gatekeeper-block> > > I have these IDs: > Developer ID Installer > Developer ID Application > > DropDMG shows in its preferences the 'Developer ID Application’ that is used > to sign the installer. That should be used and not 'Developer ID Installer’? > > > Anyone have any guidance on this? > > > And this all doesn’t have anything to do with Notarization? That’s another > step for the future? > > Thanks for any help! > > Peter Bogdanoff > ArtsInteractive _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
