Re: notarizing DMG fails - solved
Thanks Phil. @all I've updated the lesson at https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore now and added detailed information about package installers. So it now contains also information about how to create,sign and notarize package installers or package installers on dmg. It would be really awesome, if someone could check it. I needed to insert some additional steps and i really hope that i did not forget to adjust some references to internal steps. So please let me if you find any errors, typos or wrong information. Thanks. Matthias > Am 05.05.2021 um 19:49 schrieb Phil Davis via use-livecode > : > > Thank you Matthias! Your tools make my life SO much easier! You have > done a great service for this community. > > Phil Davis > > > On 5/5/21 2:20 AM, matthias rebbe via use-livecode wrote: >>> Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode >>> : >>> >>> Thank you all for helping my lost soul in Apples notarizing nirvana >>> >>> Tiemo >>> >>> P.S. >>> Matthias, perhaps you want to add this in your great helpfile - without >>> that it would have taken weeks for me! >>> >> I am currently working on it. ;) >> First i will just add a note, but later, when i have more free time i will >> enhance it to describe all more detailed. >> >> The Helper Stack will also get an update to support package installers. But >> it takes some time. >> >> >> >>> -Ursprüngliche Nachricht- >>> Von: use-livecode Im Auftrag von >>> matthias rebbe via use-livecode >>> Gesendet: Mittwoch, 5. Mai 2021 10:31 >>> An: How to use LiveCode >>> Cc: matthias_livecode_150...@m-r-d.de >>> Betreff: Re: notarizing DMG fails >>> >>> Tiemo, >>> >>> i think i found the solution. I tried here myself and did als get the error >>> "this identity cannot be used for signing code" when using the Developer ID >>> Installer certificate for signing the .pkg. >>> According to Apple (see point 2) >>> https://help.apple.com/xcode/mac/current/#/deve51ce7c3d >>> >>> you have to use the tool productsign to sign the package installer. >>> >>> So the syntax is like this >>> >>> productsign --sign >>> >>> >>> Example >>> productsign --sign "Developer ID Installer: Matthias Rebbe ()" >>> "/users/matthias/LC/builts/test/test.pkg" >>> "/users/matthias/LC/builts/test/test_signed.pkg" >>> >>> After successful signing i got this messages in Terminal >>> >>> productsign: using timestamp authority for signature >>> productsign: signing product with identity "Developer ID Installer: >>> Matthias Rebbe ()" from keychain >>> /Users/matthias/Library/Keychains/login.keychain-db >>> productsign: adding certificate "Developer ID Certification Authority" >>> productsign: adding certificate "Apple Root CA" >>> productsign: Wrote signed product archive to >>> /users/matthias/LC/builts/test/test_signed.pkg >>> >>> >>> Regards >>> >>> - >>> Matthias Rebbe >>> Life Is Too Short For Boring Code >> >> ___ >> 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 > > -- > Phil Davis > 503-307-4363 > > > ___ > 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 ___ 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
Re: notarizing DMG fails - solved
Thank you Matthias! Your tools make my life SO much easier! You have done a great service for this community. Phil Davis On 5/5/21 2:20 AM, matthias rebbe via use-livecode wrote: >> Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode >> : >> >> Thank you all for helping my lost soul in Apples notarizing nirvana >> >> Tiemo >> >> P.S. >> Matthias, perhaps you want to add this in your great helpfile - without that >> it would have taken weeks for me! >> > I am currently working on it. ;) > First i will just add a note, but later, when i have more free time i will > enhance it to describe all more detailed. > > The Helper Stack will also get an update to support package installers. But > it takes some time. > > > >> -Ursprüngliche Nachricht- >> Von: use-livecode Im Auftrag von >> matthias rebbe via use-livecode >> Gesendet: Mittwoch, 5. Mai 2021 10:31 >> An: How to use LiveCode >> Cc: matthias_livecode_150...@m-r-d.de >> Betreff: Re: notarizing DMG fails >> >> Tiemo, >> >> i think i found the solution. I tried here myself and did als get the error >> "this identity cannot be used for signing code" when using the Developer ID >> Installer certificate for signing the .pkg. >> According to Apple (see point 2) >> https://help.apple.com/xcode/mac/current/#/deve51ce7c3d >> >> you have to use the tool productsign to sign the package installer. >> >> So the syntax is like this >> >> productsign --sign >> >> >> Example >> productsign --sign "Developer ID Installer: Matthias Rebbe ()" >> "/users/matthias/LC/builts/test/test.pkg" >> "/users/matthias/LC/builts/test/test_signed.pkg" >> >> After successful signing i got this messages in Terminal >> >> productsign: using timestamp authority for signature >> productsign: signing product with identity "Developer ID Installer: Matthias >> Rebbe ()" from keychain >> /Users/matthias/Library/Keychains/login.keychain-db >> productsign: adding certificate "Developer ID Certification Authority" >> productsign: adding certificate "Apple Root CA" >> productsign: Wrote signed product archive to >> /users/matthias/LC/builts/test/test_signed.pkg >> >> >> Regards >> >> - >> Matthias Rebbe >> Life Is Too Short For Boring Code > > ___ > 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 -- Phil Davis 503-307-4363 ___ 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
Re: Problems with Multiple Monitors
On 5/5/2021 12:15 PM, Mark Wieder via use-livecode wrote: On 5/5/21 8:53 AM, Paul Dupuis via use-livecode wrote: I'm afraid I can't help with this. A good while ago, I moved to my own centerWindow command that doesn't use screenLoc, but uses the stack's (window's the screen property 9for the line number of the screenRect the stack is on) and the screenRects to get the rect of the monitor the window is on. I then use that monitor's rect to get the center coordinates and then adjust for any menubar or taskbar, etc to get the effective center for that monitor to center a window (I think I actually now use the working screenRects or effective screenRects or maybe the effective working screenRects ;-) Yep - that's what I do as well. A couple of useful enhancements would be the screenLocs # return a list the screenLoc(2) # allow a parameter for the screen number I'd also like to see 'effective' and 'working' applied to the screenRect and screenRects and screenRect(the screen of window X) ___ 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
Re: Problems with Multiple Monitors
On 5/5/2021 12:15 PM, Mark Wieder via use-livecode wrote: On 5/5/21 8:53 AM, Paul Dupuis via use-livecode wrote: I'm afraid I can't help with this. A good while ago, I moved to my own centerWindow command that doesn't use screenLoc, but uses the stack's (window's the screen property 9for the line number of the screenRect the stack is on) and the screenRects to get the rect of the monitor the window is on. I then use that monitor's rect to get the center coordinates and then adjust for any menubar or taskbar, etc to get the effective center for that monitor to center a window (I think I actually now use the working screenRects or effective screenRects or maybe the effective working screenRects ;-) Yep - that's what I do as well. A couple of useful enhancements would be the screenLocs # return a list the screenLoc(2) # allow a parameter for the screen number +1 to both of those! ___ 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
Re: Problems with Multiple Monitors
On 5/5/21 8:53 AM, Paul Dupuis via use-livecode wrote: I'm afraid I can't help with this. A good while ago, I moved to my own centerWindow command that doesn't use screenLoc, but uses the stack's (window's the screen property 9for the line number of the screenRect the stack is on) and the screenRects to get the rect of the monitor the window is on. I then use that monitor's rect to get the center coordinates and then adjust for any menubar or taskbar, etc to get the effective center for that monitor to center a window (I think I actually now use the working screenRects or effective screenRects or maybe the effective working screenRects ;-) Yep - that's what I do as well. A couple of useful enhancements would be the screenLocs # return a list the screenLoc(2) # allow a parameter for the screen number -- Mark Wieder ahsoftw...@gmail.com ___ 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
Re: Problems with Multiple Monitors
On 5/5/2021 11:42 AM, Richard Gaskin via use-livecode wrote: Thanks, Paul, and the others who chimed in. I'm familiar with the documented features for screen metrics, just trying to determine if the rect of the main screen no longer being the reference point for metrics is a change/bug I need to be concerned about? And this got me thinking about screenLoc: if the main screen isn't the reference point, then is the screenLoc adjusted for the non-0,0 corner or is it based on the sum boundary of all connected monitors? And is any of this platform-specific? Or different from how it's been since the plural screenRects was introduced? I'm afraid I can't help with this. A good while ago, I moved to my own centerWindow command that doesn't use screenLoc, but uses the stack's (window's the screen property 9for the line number of the screenRect the stack is on) and the screenRects to get the rect of the monitor the window is on. I then use that monitor's rect to get the center coordinates and then adjust for any menubar or taskbar, etc to get the effective center for that monitor to center a window (I think I actually now use the working screenRects or effective screenRects or maybe the effective working screenRects ;-) ___ 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
Re: Problems with Multiple Monitors
Thanks, Paul, and the others who chimed in. I'm familiar with the documented features for screen metrics, just trying to determine if the rect of the main screen no longer being the reference point for metrics is a change/bug I need to be concerned about? And this got me thinking about screenLoc: if the main screen isn't the reference point, then is the screenLoc adjusted for the non-0,0 corner or is it based on the sum boundary of all connected monitors? And is any of this platform-specific? Or different from how it's been since the plural screenRects was introduced? -- Richard Gaskin Fourth World Systems Paul Dupuis wrote: On 5/4/2021 8:20 PM, Richard Gaskin via use-livecode wrote: Paul Dupuis wrote: With multiple monitor, zero vertical is the top of the top most monitor - regardless of whether it is the primary monitor or not. If the screenRect is no longer based on the main monitor, what is the screenloc? In a multi-monitor setup, with metrics like that how can one be expected to center a window? screenRect still returns the rect of the main monitor and the first line of the screenRects is still the rect of the main or primary monitor (the one with the menubar/taskbar) however, you can not count on its left,top of the primary monitor being 0,0 in a multiple monitor configuration. It may be or it may not be depending of where the second (or more) monitors are in relation to the primary one. Took me a while to figure this one out based on a customer's reported symptoms! Also, if you think you may have customers with multiple monitors, the on desktopChanged message is your friend. I ran into a customer who would often leave HyperRESEARCH running, minimized or hidden, and then remove a external monitor from their laptop to go. LiveCode still thinks the monitor is attached and when they placed HR windows on that external monitor, those windows were no visible or accessible (unless they quit and restarted HR). Now I have a desktopChanged handler that gets the screenRects and checks to see if every open window is inside a current screenRect and moves the windows if needed. ___ 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
Re: Problems with Multiple Monitors
On 5/4/2021 8:20 PM, Richard Gaskin via use-livecode wrote: Paul Dupuis wrote: With multiple monitor, zero vertical is the top of the top most monitor - regardless of whether it is the primary monitor or not. If the screenRect is no longer based on the main monitor, what is the screenloc? In a multi-monitor setup, with metrics like that how can one be expected to center a window? screenRect still returns the rect of the main monitor and the first line of the screenRects is still the rect of the main or primary monitor (the one with the menubar/taskbar) however, you can not count on its left,top of the primary monitor being 0,0 in a multiple monitor configuration. It may be or it may not be depending of where the second (or more) monitors are in relation to the primary one. Took me a while to figure this one out based on a customer's reported symptoms! Also, if you think you may have customers with multiple monitors, the on desktopChanged message is your friend. I ran into a customer who would often leave HyperRESEARCH running, minimized or hidden, and then remove a external monitor from their laptop to go. LiveCode still thinks the monitor is attached and when they placed HR windows on that external monitor, those windows were no visible or accessible (unless they quit and restarted HR). Now I have a desktopChanged handler that gets the screenRects and checks to see if every open window is inside a current screenRect and moves the windows if needed. -- Paul ___ 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
Re: Problems with Multiple Monitors
I hear ya, but with this list we Illegitimi non carborundum! Roger > On May 5, 2021, at 4:36 AM, Martin Koob via use-livecode > wrote: > > I will have to deal with reprogramming the wetware and the muscle memory > which at my age may be a much more difficult process. The ole wetware ain’t > as moist and flexible as it once was ;-) ___ 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
Re: Problems with Multiple Monitors
Hi Roger Thanks, I’ll try that. However then I will have to deal with reprogramming the wetware and the muscle memory which at my age may be a much more difficult process. The ole wetware ain’t as moist and flexible as it once was ;-) Martin > On May 4, 2021, at 8:17 PM, Roger Guay via use-livecode > wrote: > > Hi Martin, > > I have the same setup . . . second monitor on top of my MBP. I solved the > problem by unchecking “Displays have separate Spaces” in the Mission Control > System Preferences. > > > Roger > >> On May 4, 2021, at 3:17 PM, Martin Koob via use-livecode >> wrote: >> >> Hi >> >> I have found that when I arrange monitors on my MacBook Pro I can’t position >> the second monitor above the main monitor(the one with the menu bar). If I >> do odd things happen. Just so happens I that is the space that I have for a >> second monitor is on a stand above the screen of my MacBook Pro. So I had >> to position my second monitor to the left of my main monitor. I am then >> able to work on LiveCode in either monitor. The only thing I had to do was >> re-train my brain that moving my mouse left was actually moving it up to my >> second monitor. Now it is second nature. >> >> It is a really odd workaround and if the bug ever got fixed and I did in >> fact go back to to having the monitor arrangement with the second monitor >> above the main monitor I would probably develop carpal tunnel syndrome or >> maybe tennis elbow or some other musculoskeletal disorder from my mouse >> hand skidding off the mouse pad and hitting the laptop every time I want to >> go to the second monitor sitting above my laptop. >> >> Martin >> >> >>> On May 4, 2021, at 5:46 PM, Paul Dupuis via use-livecode >>> wrote: >>> >>> On 5/4/2021 5:32 PM, Fred Moyer via use-livecode wrote: Anyone having problems with multiple monitors and LC? I’m running 9.6.1 - Mac. I have a feeling LC is confused because I like to connect and disconnect monitors from my MacBook Pro. (Even the MacOS sometimes gets confused.) But now LC is doing crazy things — even when no external monitors are connected. I’ll move the mouse to the top of a stack window, and ask for the Mouseloc and it will return something like "100,-60”. If I click a button in the middle of the stack, the click will register in an object the 60 pixels above that. It’s not always 60 — the wrongness changed as I move the stack around. Other times it works fine. I can’t find a pattern to set it off. Any suggestions? Thanks. Fred >>> >>> With multiple monitor, zero vertical is the top of the top most monitor - >>> regardless of whether it is the primary monitor or not. The on >>> desktopChanged message may also be helpful as it is sent when the >>> displays/monitors change >>> >>> >>> ___ >>> 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 >> >> >> ___ >> 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 > > ___ > 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 ___ 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
Re: notarizing DMG fails - solved
> Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode > : > > Thank you all for helping my lost soul in Apples notarizing nirvana > > Tiemo > > P.S. > Matthias, perhaps you want to add this in your great helpfile - without that > it would have taken weeks for me! > I am currently working on it. ;) First i will just add a note, but later, when i have more free time i will enhance it to describe all more detailed. The Helper Stack will also get an update to support package installers. But it takes some time. > > -Ursprüngliche Nachricht- > Von: use-livecode Im Auftrag von > matthias rebbe via use-livecode > Gesendet: Mittwoch, 5. Mai 2021 10:31 > An: How to use LiveCode > Cc: matthias_livecode_150...@m-r-d.de > Betreff: Re: notarizing DMG fails > > Tiemo, > > i think i found the solution. I tried here myself and did als get the error > "this identity cannot be used for signing code" when using the Developer ID > Installer certificate for signing the .pkg. > According to Apple (see point 2) > https://help.apple.com/xcode/mac/current/#/deve51ce7c3d > > you have to use the tool productsign to sign the package installer. > > So the syntax is like this > > productsign --sign > > > Example > productsign --sign "Developer ID Installer: Matthias Rebbe ()" > "/users/matthias/LC/builts/test/test.pkg" > "/users/matthias/LC/builts/test/test_signed.pkg" > > After successful signing i got this messages in Terminal > > productsign: using timestamp authority for signature > productsign: signing product with identity "Developer ID Installer: Matthias > Rebbe ()" from keychain > /Users/matthias/Library/Keychains/login.keychain-db > productsign: adding certificate "Developer ID Certification Authority" > productsign: adding certificate "Apple Root CA" > productsign: Wrote signed product archive to > /users/matthias/LC/builts/test/test_signed.pkg > > > Regards > > - > Matthias Rebbe > Life Is Too Short For Boring Code ___ 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
AW: notarizing DMG fails - solved
exactly, that’s the culprit! to make matters worse you can use codesign also for packages and even verifying that codesign returns a valid codesign, but using codesign for packages ignores the content of the package and only looks for the envelope, what is useless. So two issues are vital when codesigning packages: Using the Developer Installer ID certificate And not using codesign, but productsign Thank you all for helping my lost soul in Apples notarizing nirvana Tiemo P.S. Matthias, perhaps you want to add this in your great helpfile - without that it would have taken weeks for me! -Ursprüngliche Nachricht- Von: use-livecode Im Auftrag von matthias rebbe via use-livecode Gesendet: Mittwoch, 5. Mai 2021 10:31 An: How to use LiveCode Cc: matthias_livecode_150...@m-r-d.de Betreff: Re: notarizing DMG fails Tiemo, i think i found the solution. I tried here myself and did als get the error "this identity cannot be used for signing code" when using the Developer ID Installer certificate for signing the .pkg. According to Apple (see point 2) https://help.apple.com/xcode/mac/current/#/deve51ce7c3d you have to use the tool productsign to sign the package installer. So the syntax is like this productsign --sign Example productsign --sign "Developer ID Installer: Matthias Rebbe ()" "/users/matthias/LC/builts/test/test.pkg" "/users/matthias/LC/builts/test/test_signed.pkg" After successful signing i got this messages in Terminal productsign: using timestamp authority for signature productsign: signing product with identity "Developer ID Installer: Matthias Rebbe ()" from keychain /Users/matthias/Library/Keychains/login.keychain-db productsign: adding certificate "Developer ID Certification Authority" productsign: adding certificate "Apple Root CA" productsign: Wrote signed product archive to /users/matthias/LC/builts/test/test_signed.pkg Regards - Matthias Rebbe Life Is Too Short For Boring Code > Am 05.05.2021 um 09:35 schrieb matthias rebbe via use-livecode > : > > Timo, > > .app -> Developer ID Application > .pkg -> Developer ID Installer > .dmg -> Developer ID Application > > > > - > Matthias Rebbe > Life Is Too Short For Boring Code > >> Am 05.05.2021 um 08:56 schrieb Tiemo via use-livecode >> : >> >> Hi Panos, >> thanks for jumping in >> >> I am on macOS 11.2.3 and created the certificates pretty freshly two weeks >> ago. >> Xcode-select -p doesn't returns any version# at all, it just returns >> a path: "/Applications/Xcode.app/Content/Developer/ >> Xcodebuild -version shows Xcode 12.5 build 12E262 I now >> (re-?)installed the command line tools by xcode-select -- install But >> xcode-select -p still doesn't shows any version# ??? >> I now downloaded the Apple Worldwide Developer Relations Intermediate >> Certificate. Actually I am not sure, if it was there before (I didn't >> checked it before) >> >> I will later test again from the scratch >> >> But I am still unsure if I may use the " Developer ID Application" >> certificate also for the pkg and dmg or if I have to use the "Developer ID >> Installer" certificate for the pkg and dmg? >> >> Thanks >> >> Tiemo >> >> >> >> -Ursprüngliche Nachricht- >> Von: use-livecode Im Auftrag >> von panagiotis merakos via use-livecode >> Gesendet: Dienstag, 4. Mai 2021 18:19 >> An: How to use LiveCode >> Cc: panagiotis merakos >> Betreff: Re: notarizing DMG fails >> >> Hello Tiemo, >> >> When did you create these certificates? And what is your MacOS version, and >> the Xcode version returned if you type "xcode-select -p" in a Terminal? I am >> wondering if you need to install the new Apple Worldwide Developer Relations >> Intermediate Certificate: >> >> https://developer.apple.com/support/wwdr-intermediate-certificate/ >> >> You can find it here: >> >> https://developer.apple.com/support/expiration/ >> >> Kind regards, >> Panos >> -- >> >> On Tue, 4 May 2021 at 19:02, Tiemo via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >>> Hi Matthias, >>> >>> still struggeling ... >>> >>> I have two developer certificates in my keychain: >>> Developer ID Installer : >>> Developer ID Application: >>> >>> Using the Application certificate on the app and pkg and dmg, all >>> codesigning is fine, even when verifying it, but I get the "The >>> binary is not signed" error in the notarization log, when notarizing the >>> dmg ??? >>> Using the Installer certificate on the pkg, I get already the error >>> when codesigning the pkg "this identity cannot be used for signing code" ??? >>> >>> All errors are the same, either using the tool "Packages" or >>> creating the package on command line by pkgbuild (productbuild is >>> only for builing appStore apps, as far as I see it) >>> >>> I must be missing something obvious >>> >>> Any other ideas? >>> Tiemo >>> >>> >>> -Ursprüngliche Nachricht- >>> Von: use-livecode Im Auftrag >>> von matthias rebbe via u
Re: notarizing DMG fails
Tiemo, i think i found the solution. I tried here myself and did als get the error "this identity cannot be used for signing code" when using the Developer ID Installer certificate for signing the .pkg. According to Apple (see point 2) https://help.apple.com/xcode/mac/current/#/deve51ce7c3d you have to use the tool productsign to sign the package installer. So the syntax is like this productsign --sign Example productsign --sign "Developer ID Installer: Matthias Rebbe ()" "/users/matthias/LC/builts/test/test.pkg" "/users/matthias/LC/builts/test/test_signed.pkg" After successful signing i got this messages in Terminal productsign: using timestamp authority for signature productsign: signing product with identity "Developer ID Installer: Matthias Rebbe ()" from keychain /Users/matthias/Library/Keychains/login.keychain-db productsign: adding certificate "Developer ID Certification Authority" productsign: adding certificate "Apple Root CA" productsign: Wrote signed product archive to /users/matthias/LC/builts/test/test_signed.pkg Regards - Matthias Rebbe Life Is Too Short For Boring Code > Am 05.05.2021 um 09:35 schrieb matthias rebbe via use-livecode > : > > Timo, > > .app -> Developer ID Application > .pkg -> Developer ID Installer > .dmg -> Developer ID Application > > > > - > Matthias Rebbe > Life Is Too Short For Boring Code > >> Am 05.05.2021 um 08:56 schrieb Tiemo via use-livecode >> : >> >> Hi Panos, >> thanks for jumping in >> >> I am on macOS 11.2.3 and created the certificates pretty freshly two weeks >> ago. >> Xcode-select -p doesn't returns any version# at all, it just returns a path: >> "/Applications/Xcode.app/Content/Developer/ >> Xcodebuild -version shows Xcode 12.5 build 12E262 >> I now (re-?)installed the command line tools by xcode-select -- install >> But xcode-select -p still doesn't shows any version# ??? >> I now downloaded the Apple Worldwide Developer Relations Intermediate >> Certificate. Actually I am not sure, if it was there before (I didn't >> checked it before) >> >> I will later test again from the scratch >> >> But I am still unsure if I may use the " Developer ID Application" >> certificate also for the pkg and dmg or if I have to use the "Developer ID >> Installer" certificate for the pkg and dmg? >> >> Thanks >> >> Tiemo >> >> >> >> -Ursprüngliche Nachricht- >> Von: use-livecode Im Auftrag von >> panagiotis merakos via use-livecode >> Gesendet: Dienstag, 4. Mai 2021 18:19 >> An: How to use LiveCode >> Cc: panagiotis merakos >> Betreff: Re: notarizing DMG fails >> >> Hello Tiemo, >> >> When did you create these certificates? And what is your MacOS version, and >> the Xcode version returned if you type "xcode-select -p" in a Terminal? I am >> wondering if you need to install the new Apple Worldwide Developer Relations >> Intermediate Certificate: >> >> https://developer.apple.com/support/wwdr-intermediate-certificate/ >> >> You can find it here: >> >> https://developer.apple.com/support/expiration/ >> >> Kind regards, >> Panos >> -- >> >> On Tue, 4 May 2021 at 19:02, Tiemo via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >>> Hi Matthias, >>> >>> still struggeling ... >>> >>> I have two developer certificates in my keychain: >>> Developer ID Installer : >>> Developer ID Application: >>> >>> Using the Application certificate on the app and pkg and dmg, all >>> codesigning is fine, even when verifying it, but I get the "The binary >>> is not signed" error in the notarization log, when notarizing the dmg ??? >>> Using the Installer certificate on the pkg, I get already the error >>> when codesigning the pkg "this identity cannot be used for signing code" ??? >>> >>> All errors are the same, either using the tool "Packages" or creating >>> the package on command line by pkgbuild (productbuild is only for >>> builing appStore apps, as far as I see it) >>> >>> I must be missing something obvious >>> >>> Any other ideas? >>> Tiemo >>> >>> >>> -Ursprüngliche Nachricht- >>> Von: use-livecode Im Auftrag >>> von matthias rebbe via use-livecode >>> Gesendet: Dienstag, 4. Mai 2021 13:49 >>> An: How to use LiveCode >>> Cc: matthias_livecode_150...@m-r-d.de >>> Betreff: Re: notarizing DMG fails >>> >>> Tiemo, >>> >>> you can create 2 different installer certificates in you Apple >>> developer account. >>> One is called 'Mac Installer Distribution' and is used for code >>> signing installers for the Mac App Store. >>> The other one is called 'Developer ID Installer' and is used to code >>> sign your Installer Package for distribution outside of the Mac App >>> Store >>> >>> Which one did you use for signing the packager? >>> >>> And another question, how did you build the package? Did you use a 3rd >>> party tool or did you use 'productbuild' in Terminal? >>> If you used a 3rd party tool, then could you please try to create the >>> package installer usin
Re: notarizing DMG fails
Timo, .app -> Developer ID Application .pkg -> Developer ID Installer .dmg -> Developer ID Application - Matthias Rebbe Life Is Too Short For Boring Code > Am 05.05.2021 um 08:56 schrieb Tiemo via use-livecode > : > > Hi Panos, > thanks for jumping in > > I am on macOS 11.2.3 and created the certificates pretty freshly two weeks > ago. > Xcode-select -p doesn't returns any version# at all, it just returns a path: > "/Applications/Xcode.app/Content/Developer/ > Xcodebuild -version shows Xcode 12.5 build 12E262 > I now (re-?)installed the command line tools by xcode-select -- install > But xcode-select -p still doesn't shows any version# ??? > I now downloaded the Apple Worldwide Developer Relations Intermediate > Certificate. Actually I am not sure, if it was there before (I didn't checked > it before) > > I will later test again from the scratch > > But I am still unsure if I may use the " Developer ID Application" > certificate also for the pkg and dmg or if I have to use the "Developer ID > Installer" certificate for the pkg and dmg? > > Thanks > > Tiemo > > > > -Ursprüngliche Nachricht- > Von: use-livecode Im Auftrag von > panagiotis merakos via use-livecode > Gesendet: Dienstag, 4. Mai 2021 18:19 > An: How to use LiveCode > Cc: panagiotis merakos > Betreff: Re: notarizing DMG fails > > Hello Tiemo, > > When did you create these certificates? And what is your MacOS version, and > the Xcode version returned if you type "xcode-select -p" in a Terminal? I am > wondering if you need to install the new Apple Worldwide Developer Relations > Intermediate Certificate: > > https://developer.apple.com/support/wwdr-intermediate-certificate/ > > You can find it here: > > https://developer.apple.com/support/expiration/ > > Kind regards, > Panos > -- > > On Tue, 4 May 2021 at 19:02, Tiemo via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> Hi Matthias, >> >> still struggeling ... >> >> I have two developer certificates in my keychain: >> Developer ID Installer : >> Developer ID Application: >> >> Using the Application certificate on the app and pkg and dmg, all >> codesigning is fine, even when verifying it, but I get the "The binary >> is not signed" error in the notarization log, when notarizing the dmg ??? >> Using the Installer certificate on the pkg, I get already the error >> when codesigning the pkg "this identity cannot be used for signing code" ??? >> >> All errors are the same, either using the tool "Packages" or creating >> the package on command line by pkgbuild (productbuild is only for >> builing appStore apps, as far as I see it) >> >> I must be missing something obvious >> >> Any other ideas? >> Tiemo >> >> >> -Ursprüngliche Nachricht- >> Von: use-livecode Im Auftrag >> von matthias rebbe via use-livecode >> Gesendet: Dienstag, 4. Mai 2021 13:49 >> An: How to use LiveCode >> Cc: matthias_livecode_150...@m-r-d.de >> Betreff: Re: notarizing DMG fails >> >> Tiemo, >> >> you can create 2 different installer certificates in you Apple >> developer account. >> One is called 'Mac Installer Distribution' and is used for code >> signing installers for the Mac App Store. >> The other one is called 'Developer ID Installer' and is used to code >> sign your Installer Package for distribution outside of the Mac App >> Store >> >> Which one did you use for signing the packager? >> >> And another question, how did you build the package? Did you use a 3rd >> party tool or did you use 'productbuild' in Terminal? >> If you used a 3rd party tool, then could you please try to create the >> package installer using terminal command? >> >> productbuild --sign >> --component /Applications >> >> example >> productbuild --sign "Developer ID Installer: Matthias Rebbe >> (x)" --component "/users/matthias/LC/builts/test/test.app" >> /Applications "/users/matthias/downloads/MyPackager.pkg" >> >> >> But maybe it was just the wrong installer certificate >> >> Regards >> Matthias >> >> >> - >> Matthias Rebbe >> Life Is Too Short For Boring Code >> >>> Am 04.05.2021 um 12:08 schrieb Tiemo via use-livecode < >> use-livecode@lists.runrev.com>: >>> >>> Hi Matthias, >>> >>> thank you for your ideas. I tried both. >>> >>> When using just signed, but not notarized apps, packing, signing the >>> pkg, wrapping into dmg, signing the dmg, I get the same error when >>> notarizing the dmg "The binary is not signed" >>> >>> When trying to notarize the signed pkg via terminal I get the error: >>> "unable to notarize app" >>> "Upload succeeded but did not receive a RequestedUUID. Unable to >>> upload your app for notarization (-1018)" >>> >>> I also tried to use the "Installer" certificate instead of the >> "Application" >>> certificate, but trying this with codesigning the package, I get the >>> error "this identitiy cannot be used" >>> (actually I don't know for what purposes you can use the Installer >>> certificate) >>>
