We current ship a commercial app. We code sign, notarize, and staple our
App We then place it on a DMG using DropDMG, but do not code sign the
DMG. We distribute the DMG via our Web site and not the MacApp store.
QA testing on Catalina and Big Sur show only the usual "This (the DMG)
has been d
To avoid the unidentifiable developer warning in recent macOS versions, you do
need it signed. If your market is consumers, that is what they will have.
DropDMG is great.
Peter
> On Feb 4, 2021, at 8:49 AM, Klaus major-k via use-livecode
> wrote:
>
> Hi Paul,
>
>> Am 04.02.2021 um 17:46 s
Hi Paul,
> Am 04.02.2021 um 17:46 schrieb Paul Dupuis via use-livecode
> :
>
> If the App is Signed and Notarized, it is actually best NOT to sign the DMG.
> Older versions of MacOS (like Mavericks, etc.) have a problem with signed DMGs
thank you very much, very helpful!
> On 2/4/2021 11:40 AM
If the App is Signed and Notarized, it is actually best NOT to sign the
DMG. Older versions of MacOS (like Mavericks, etc.) have a problem with
signed DMGs
On 2/4/2021 11:40 AM, Klaus major-k via use-livecode wrote:
Hi friends,
quick question, now we have a Mac app, signed and notarized
and
Hi friends,
quick question, now we have a Mac app, signed and notarized
and what not, is it also neccessary for the DMG we create from
that app for distribution?
Thanks for any insight!
Best
Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
kl...@major-k.de
