How do I codesign an App?

[William Prothero]

Trevor:
By the way, I have a bunch of certificates. A link to my keychain window is:
https://www.dropbox.com/s/hlfa9tqtfrm7tyw/KeyChainCertWindow.png?dl=0 <https://www.dropbox.com/s/hlfa9tqtfrm7tyw/KeyChainCertWindow.png?dl=0>

I tried “William Prothero” as the certificate identifier. I wonder if my big bunch of certificate, acquired over the years, is confusing your stack. The basic message I get is “no identity found”.

Part of my problem is that I build up a lot of deployment items, like certificates, provisioning profiles, etc, and lose track of which ones are ok and which ones are useless or obsolete.

Do I need a different certificate for each application, or will one suffice for all OSX apps I build? Can I get rid of a bunch of them?

Best,
Bill

> On Oct 26, 2016, at 11:40 AM, William Prothero <prothero at earthednet.org> wrote:
> 
> Trevor:
> I tried your codesigning livecode app. First  I signed it with App Wrapper3, to make sure I had a good certificate. Then I tried it with your stack, using the same certificate:
> 
> I tried it using different certificate names, but basically the response was the same.
> 
> I got the response below:
> 
> chmod -R u+rw "/Users/prothero/Desktop/Plate Tectonics Explorer-V8/Plate Tectonics Explorer-V8/Plate Tectonics Explorer-V8.app"
> 
> xattr -rc "/Users/prothero/Desktop/Plate Tectonics Explorer-V8/Plate Tectonics Explorer-V8/Plate Tectonics Explorer-V8.app"
> 
> codesign --verbose --force -s "Developer ID Application: 3rd Party Mac Developer Application" "/Users/prothero/Desktop/Plate Tectonics Explorer-V8/Plate Tectonics Explorer-V8/Plate Tectonics Explorer-V8.app/Contents/MacOS/Externals/revbrowser.bundle/Contents/MacOS/revbrowser"
> 
> codesign process failed: Developer ID Application: 3rd Party Mac Developer Application: no identity found
> 
> ——————————————————
> 
> The App Wrapper installer gave me:
> link to image:  https://www.dropbox.com/s/puiwpraqaewtu23/AppWrapperWindow.png?dl=0 <https://www.dropbox.com/s/puiwpraqaewtu23/AppWrapperWindow.png?dl=0>
> 
> Thanks for providing this stack. I hope this helps and if you need any other info, let me know.
> .
> Best,
> Bill
> 
>> On Oct 26, 2016, at 5:39 AM, Trevor DeVore <lists at mangomultimedia.com> wrote:
>> 
>> On Tue, Oct 25, 2016 at 9:51 PM, William Prothero <prothero at earthednet.org>
>> wrote:
>> 
>>> Trevor:
>>> Thanks a bunch! I haven’t played with the GLX App Framework, but I will
>>> and use that code. This is something that really needs to be in the IDE.
>>> Its SUCH a common thing to do and can be so frustrating.
>>> 
>>> The other problem I get into is having a bunch of certificates that don’t
>>> work and I can’t seem to figure which one to use. I try them all, so…
>>> Anyway, the signing code looks like a natural for the IDE.
>>> 
>> 
>> Here is a gist with the code for a script-only stack that will codesign a
>> LiveCode application:
>> 
>> https://gist.github.com/trevordevore/3e91724c4573690b691510d2e2dcd2a7
>> 
>> Save the text in the gist to a file named “signOSXApplication.livecode”
>> then open the file in LiveCode (I tested in 8.1.1). Steps:
>> 
>> 1) Click the Sign Application button
>> 2) Select an application bundle that you built with LiveCode
>> 3) Enter your certificate name. Just enter the part that is unique to you.
>> For example, I enter “Blue Mango Learning Systems”. My keychain has entries
>> like “Developer ID Application: Blue Mango Learning Systems” and “3rd Party
>> Mac Developer Application: Blue Mango Learning Systems”. The code will add
>> the appropriate prefix.
>> 
>> The log field will show what is going on.
>> 
>> I tested with a simple app built from LiveCode on macOS Sierra. Last week I
>> had to add some additional code to the signing process to accommodate
>> Sierra. If you run into problems on other platforms we may need to comment
>> out the xattr call on line 60.
>> 
>> Let me know how it goes.
>> 
>> -- 
>> Trevor DeVore
>> ScreenSteps
>> www.screensteps.com    -    www.clarify-it.com
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode