Re: Signing MacOS Standalones
Thanks Paul - yes, I've got an active Apple Developer account and I've downloaded a code signing certificate for both MacOS and the iOS systems. After dragging my app to AppWrapper and immediately wrapping it AppWrapper displays "Unable to Code Sign the application - please select a valid code signing identity". It then wraps it anyway but leaves me with a "potential issue" that "CfBundle Get Info String is depricated". In any event the app wasn't code signed. When I try to use the Code Signature pull down to make a selection (changing it from 'no signature') I see 2 choices, each one available for App Store or Web Deployment. But they all display "Both Cert Missing". That's where I'm stuck. So yes, I have reached out to the guys at Ohanaware Software. I'll see if they can clear this up for me. Thanks, Ray On 5/25/2018 5:24 PM, Paul Dupuis via use-livecode wrote: I am not sure - the "no identity" seems like you may have not added your code signing certificate to AppWrapper. To verify, you have an Apple Developer account. From the Developer account, you have downloaded a code signing certificate for signing OSX desktop apps (Apple issues different certificates for signing desktop app and iOS apps). I'm sorry, but I do not remember the specifc steps to add your certificate to AppWrapper, but in the past, Ohanaware email support has been really good. Have you contacted them? On 5/25/2018 8:40 AM, Ray via use-livecode wrote: Paul thanks again for your suggestion here. I finally got some time and a Mac to try this but I ran into problems. I get a "no identity found" error from AppWrapper with no support as to how to find 'my identity'. I did find some information on Stack Overflow at: https://stackoverflow.com/questions/16036571/codesign-gives-always-no-identity-found-error-via-terminal but it's pretty cryptic and ultimately impossible to follow. In my opinion this whole thing seems like one big extortion scheme on the part of Apple Computers. To the best of my knowledge Microsoft does not impose anything like this on Windows developers. Exasperating matters, Apple routinely changes things up thus making it difficult for an organization such as Livecode to provide an accurate procedure. Nonetheless, if we can no longer save a standalone for MacOS we taken a major step backward, have we not? Please let me know what your thoughts are on this. Thanks! Ray Horsley On 5/19/2018 5:54 PM, Ray via use-livecode wrote: Many thanks Paul - I'll give this a try and post how it works out. On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote: You will still have to join Apple Developer to purchase a certificate, but then use AppWrapper (http://www.ohanaware.com/appwrapper/) On 5/19/2018 5:19 AM, Ray via use-livecode wrote: Does anybody have steps to sign Mac OS standalones? I've discovered Apple 10.12 or higher now sabotages unsigned standalones and it's a rather cryptic process to join the Apple dev club, create a certificate, and then sign an LC standalone, evidently using Terminal. Thanks in advance! Ray Horsley ___ 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 ___ 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: Signing MacOS Standalones
I am not sure - the "no identity" seems like you may have not added your code signing certificate to AppWrapper. To verify, you have an Apple Developer account. From the Developer account, you have downloaded a code signing certificate for signing OSX desktop apps (Apple issues different certificates for signing desktop app and iOS apps). I'm sorry, but I do not remember the specifc steps to add your certificate to AppWrapper, but in the past, Ohanaware email support has been really good. Have you contacted them? On 5/25/2018 8:40 AM, Ray via use-livecode wrote: > Paul thanks again for your suggestion here. I finally got some time > and a Mac to try this but I ran into problems. I get a "no identity > found" error from AppWrapper with no support as to how to find 'my > identity'. I did find some information on Stack Overflow at: > > https://stackoverflow.com/questions/16036571/codesign-gives-always-no-identity-found-error-via-terminal > > > but it's pretty cryptic and ultimately impossible to follow. In my > opinion this whole thing seems like one big extortion scheme on the > part of Apple Computers. To the best of my knowledge Microsoft does > not impose anything like this on Windows developers. Exasperating > matters, Apple routinely changes things up thus making it difficult > for an organization such as Livecode to provide an accurate > procedure. Nonetheless, if we can no longer save a standalone for > MacOS we taken a major step backward, have we not? > > Please let me know what your thoughts are on this. > > Thanks! > > Ray Horsley > > > On 5/19/2018 5:54 PM, Ray via use-livecode wrote: >> Many thanks Paul - I'll give this a try and post how it works out. >> >> >> On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote: >>> You will still have to join Apple Developer to purchase a certificate, >>> but then use AppWrapper (http://www.ohanaware.com/appwrapper/) >>> >>> On 5/19/2018 5:19 AM, Ray via use-livecode wrote: Does anybody have steps to sign Mac OS standalones? I've discovered Apple 10.12 or higher now sabotages unsigned standalones and it's a rather cryptic process to join the Apple dev club, create a certificate, and then sign an LC standalone, evidently using Terminal. Thanks in advance! Ray Horsley ___ 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 ___ 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: Signing MacOS Standalones
Paul thanks again for your suggestion here. I finally got some time and a Mac to try this but I ran into problems. I get a "no identity found" error from AppWrapper with no support as to how to find 'my identity'. I did find some information on Stack Overflow at: https://stackoverflow.com/questions/16036571/codesign-gives-always-no-identity-found-error-via-terminal but it's pretty cryptic and ultimately impossible to follow. In my opinion this whole thing seems like one big extortion scheme on the part of Apple Computers. To the best of my knowledge Microsoft does not impose anything like this on Windows developers. Exasperating matters, Apple routinely changes things up thus making it difficult for an organization such as Livecode to provide an accurate procedure. Nonetheless, if we can no longer save a standalone for MacOS we taken a major step backward, have we not? Please let me know what your thoughts are on this. Thanks! Ray Horsley On 5/19/2018 5:54 PM, Ray via use-livecode wrote: Many thanks Paul - I'll give this a try and post how it works out. On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote: You will still have to join Apple Developer to purchase a certificate, but then use AppWrapper (http://www.ohanaware.com/appwrapper/) On 5/19/2018 5:19 AM, Ray via use-livecode wrote: Does anybody have steps to sign Mac OS standalones? I've discovered Apple 10.12 or higher now sabotages unsigned standalones and it's a rather cryptic process to join the Apple dev club, create a certificate, and then sign an LC standalone, evidently using Terminal. Thanks in advance! Ray Horsley ___ 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: Signing MacOS Standalones
Many thanks Paul - I'll give this a try and post how it works out. On 5/19/2018 1:47 PM, Paul Dupuis via use-livecode wrote: You will still have to join Apple Developer to purchase a certificate, but then use AppWrapper (http://www.ohanaware.com/appwrapper/) On 5/19/2018 5:19 AM, Ray via use-livecode wrote: Does anybody have steps to sign Mac OS standalones? I've discovered Apple 10.12 or higher now sabotages unsigned standalones and it's a rather cryptic process to join the Apple dev club, create a certificate, and then sign an LC standalone, evidently using Terminal. Thanks in advance! Ray Horsley ___ 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: Signing MacOS Standalones
You will still have to join Apple Developer to purchase a certificate, but then use AppWrapper (http://www.ohanaware.com/appwrapper/) On 5/19/2018 5:19 AM, Ray via use-livecode wrote: > Does anybody have steps to sign Mac OS standalones? I've discovered > Apple 10.12 or higher now sabotages unsigned standalones and it's a > rather cryptic process to join the Apple dev club, create a > certificate, and then sign an LC standalone, evidently using Terminal. > > Thanks in advance! > > Ray Horsley > > ___ > 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
Signing MacOS Standalones
Does anybody have steps to sign Mac OS standalones? I've discovered Apple 10.12 or higher now sabotages unsigned standalones and it's a rather cryptic process to join the Apple dev club, create a certificate, and then sign an LC standalone, evidently using Terminal. Thanks in advance! Ray Horsley ___ 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
Signing MacOS Standalones
Does anybody have steps to sign Mac OS standalones? I've discovered Apple 10.12 or higher now sabotages unsigned standalones and it's a rather cryptic process to join the Apple dev club, create a certificate, and then sign an LC standalone, evidently using Terminal. Thanks in advance! Ray Horsley ___ 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