Bill, thanks for staying with me. I will report on my success, if I have any…
Cheer Graham > On 17 Jan 2017, at 22:55, William Prothero via use-livecode > <[email protected]> wrote: > > I “think” that once you get the certificate into keychain, you no longer need > to worry about “keys”. > The main thing is to have, for standalones, one named: “Developer ID > Application: xxxxxx” for the app. I think, if you have an installer and you > sign it, it will use one named “Developer ID Installer: xxxxxxx”. > > Mine are also in the “login” section. I don’t know the whys and wherefor’s of > that, but it works, so….. who am I to complain? > By the way, when I download the disc image, I still get a message cautioning > me that the software was downloaded from the internet. But, no more scary > “Unknown Developer” messages. > > Best, > Bill > >> On Jan 17, 2017, at 10:01 AM, Graham Samuel via use-livecode >> <[email protected]> wrote: >> >> Not quite out of the wood yet. I have actually generated the certificates, >> and got them into my KeyChain, but not exactly as I expected. I get this >> from the Apple Developer Portal: >> >>> Download, Install and Backup >>> Download your certificate to your Mac, then double click the .cer file to >>> install in Keychain Access. Make sure to save a backup copy of your private >>> and public keys somewhere secure. >> >> Double-clicking produced an incomprehensible error message to the effect >> that I was importing the certificates into the wrong place, so I followed a >> clue in the message and imported the certificates into the ‘login’ section - >> with no idea what that means. So far so good. I also copied the certificates >> to a safe place in cyberspace (there will also be automatic local backups). >> But what does the second sentence mean? Are the keys mentioned part of the >> certificate, and if they aren’t, how can I access them? Maybe the code >> signing process itself will solve this problem, but I would like to be >> clearer about where these keys are now. >> >> [sigh…] >> >> If anyone has time to explain, as ever I will be grateful. >> >> Graham >> >>> On 17 Jan 2017, at 17:59, prothero--- via use-livecode >>> <[email protected]> wrote: >>> >>> Graham, >>> For me, one problem is that I use the signing and deployment system so >>> seldom that I forget the idiosyncrasies when I delve back not the Apple >>> Developer site. I then may duplicate certificates or provisioning profiles, >>> and that confuses everything. One of the most useful buttons I clicked, on >>> App Wrapper 3 (or was it Monte's stack) listed my certificates and warned >>> me of duplicates. Them, when OS's get upgraded and Xcode versions change, >>> it can get more of a mess. >>> >>> Wouldn't it be wonderful if there was a livecode stack that could examine >>> your setup and figure all this out? I did get a lot of useful information >>> from the log files in Monte's signing app, though. >>> >>> Best, >>> Bill >>> >>> William Prothero >>> http://es.earthednet.org >>> >>>> On Jan 17, 2017, at 8:39 AM, Graham Samuel via use-livecode >>>> <[email protected]> wrote: >>>> >>>> Bill, thanks to you and to the ever-helpful Matthias. I have in fact got >>>> used to dropDMG, so I will probably stick to that. I do already have a >>>> link to the Trevor/Monte signing app, so it looks as if this is all coming >>>> together. >>>> >>>> I wonder if we are in the minority in finding all this such a PITA. There >>>> are after all a lot of successful LiveCode developers, but these >>>> deployment issues don’t appear that often on this list. Yet I can’t >>>> believe that anyone could find this stuff straightforward when they first >>>> try it. >>>> >>>> Onward! >>>> >>>> Thanks again >>>> >>>> Graham >>>> >>>>> On 17 Jan 2017, at 17:16, prothero--- via use-livecode >>>>> <[email protected]> wrote: >>>>> >>>>> Graham, >>>>> I've had similar hair pulling experiences. Mathias' instructions are >>>>> great initial steps. What you need to do after you get the developer >>>>> certificate and get it into your keychain, is to actually do the signing. >>>>> I've tried App Wrapper 3, which a lot of folks have used, but found that >>>>> it somehow messed with reading files that I needed for my app, and once >>>>> signed, wouldn't work. Rather that debug what was happening, I tried the >>>>> livecode signing app distributed by Monte and/or Trevor. It worked like a >>>>> charm. The last step was to make a disc image that could be downloaded >>>>> from a web site. I tried (not exactly sure of the precise names) dropDMG >>>>> and DMGcanvas. I found DMG canvas to be the easiest to use. >>>>> >>>>> That's it. You might search the list emails to find the link to download >>>>> the signing stack. I am not on my work computer now, but will post it if >>>>> you can't find it. >>>>> >>>>> Good luck, >>>>> Bill >>>>> >>>>> William Prothero >>>>> http://es.earthednet.org >>>>> >>>>>> On Jan 17, 2017, at 3:50 AM, Matthias Rebbe via use-livecode >>>>>> <[email protected]> wrote: >>>>>> >>>>>> Graham, >>>>>> >>>>>> - in your developer account select “Mac OS X” in the dropdown menu on >>>>>> the left side above the word “Certificates” >>>>>> - then click “All” under “Certifcates” on the left side >>>>>> - click the “+” sign on the right side (near the loupe) >>>>>> - in the next page select “Developer ID” near the bottom >>>>>> - click “continue” >>>>>> - on the next page select either “Developer ID Application” or >>>>>> “Developer ID Installer” >>>>>> - on the next page read the instructions how to create the Creator >>>>>> Signing Request >>>>>> or click continue right away if you have already created that file >>>>>> - on the next page you are able to upload your file >>>>>> - press continue >>>>>> >>>>>> Your certificate should be created. >>>>>> >>>>>> I just ran through it just to write this description, but cannot go >>>>>> further because i have all my certificates already. >>>>>> >>>>>> So maybe you have to click some mor “continue” buttons. I am not sure. >>>>>> But at least now you know where to upload that file. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Matthias >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Matthias Rebbe >>>>>> Bramkampsieke 13 >>>>>> 32312 Lübbecke >>>>>> Tel +49 5741 310000 >>>>>> +49 160 5504462 >>>>>> Fax: +49 5741 310002 >>>>>> eMail: [email protected] <mailto:[email protected]> >>>>>> >>>>>> BR5 Konverter - BR5 -> MP3 >>>>>> <http://matthiasrebbe.eu/portfolio/produkte/brx/> >>>>>>> Am 17.01.2017 um 12:21 schrieb Graham Samuel via use-livecode >>>>>>> <[email protected] <mailto:[email protected]>>: >>>>>>> >>>>>>> Having more or less sorted code signing for a Windows app - thanks to >>>>>>> contributors to this list - I am now trying to do the same for the Mac, >>>>>>> but I have clearly missed some massive chunk of the work flow. >>>>>>> >>>>>>> I’m a registered developer. I want to distribute my apps outside of the >>>>>>> Apple App Store. I realise that I have to generate a Certificate >>>>>>> Signing Request (actually two, one for the app itself and one for its >>>>>>> installer): I have done this, but now I am stuck. It says in the very >>>>>>> convoluted Apple documentation (convoluted if you’re not going down the >>>>>>> XCode/Apple Store path): >>>>>>> >>>>>>>> Upload the certificate request to the certificate authority (for >>>>>>>> example, to Apple using the developer portal, as part of the >>>>>>>> certificate generation flow). >>>>>>> I cannot see a way to do this in the Developer Portal. Obviously >>>>>>> thousands of people have done it, but I just can’t see how. >>>>>>> >>>>>>> TIA for any nice clear simple explanation! >>>>>>> >>>>>>> Graham >>>>>>> >>>>>>> I’m even more in need of a LiveCode app deployment guide than ever… >>>>>>> _______________________________________________ >>>>>>> use-livecode mailing list >>>>>>> [email protected] <mailto:[email protected]> >>>>>>> Please visit this url to subscribe, unsubscribe and manage your >>>>>>> subscription preferences: >>>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>>>>> >>>>>> _______________________________________________ >>>>>> use-livecode mailing list >>>>>> [email protected] >>>>>> Please visit this url to subscribe, unsubscribe and manage your >>>>>> subscription preferences: >>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>>>> >>>>> >>>>> _______________________________________________ >>>>> use-livecode mailing list >>>>> [email protected] >>>>> Please visit this url to subscribe, unsubscribe and manage your >>>>> subscription preferences: >>>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>>> >>>> >>>> _______________________________________________ >>>> use-livecode mailing list >>>> [email protected] >>>> Please visit this url to subscribe, unsubscribe and manage your >>>> subscription preferences: >>>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> >>> _______________________________________________ >>> use-livecode mailing list >>> [email protected] >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> _______________________________________________ >> use-livecode mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
