I tried that but I don't keep Xcode in the root of the Applications folder
and the stack gave a warning. When I moved it there, the Xcode commands
couldn't find it because I'd set the Xcode default to a copy in a subfolder.
Maybe a future update can determine the user's Xcode location. I have three
copies because different versions of LC require different versions of Xcode.
What took the most time was figuring out what was wrong.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On April 13, 2021 6:26:02 PM matthias rebbe via use-livecode
<use-livecode@lists.runrev.com> wrote:
Couldn't you search for the ASC provider in the helper stack pressing the
"Loupe" icon in the general settings?
-
Matthias Rebbe
Life Is Too Short For Boring Code
Am 14.04.2021 um 01:12 schrieb J. Landman Gay via use-livecode
<use-livecode@lists.runrev.com>:
Cool. Thanks. I do keep NotarizationHelper in my plugins folder since I use
it frequently.
I probably will continue with the manual method for a while though, since I
have three different apps to notarize and I have to update the General
settings each time. Maybe later I'll revise your script to fill in the data
for me.
What I did not realize until I wasted a lot of time today is that the ASC
changes depending on the app password, the ID Application, or something
else I can't identify. It kept telling me I wasn't a member of my own
developer account. I finally ran the Terminal command that returns all the
ASCs and my ASC was different than it was before.
People who are a member of only one account won't have that problem, but it
took me a long time to figure out what was wrong. Once I had the right ASC
your helper did its work gracefully.
On 4/13/21 2:17 PM, matthias rebbe via use-livecode wrote:
Jacque,
and if put the that NotarizerHelperStack into the plugins folder and if you
add the below code to your stack script
then you can directly code sign and notarize the created macOS standalone
right after it was built. ;)
on standaloneSaved pFolderSavedIn
if the cRevStandaloneSettings["MacOSX x86-64"] of this stack is true
then
answer "Do you want to notarize?" with "yes" or "No"
if it ="yes"
then
put pFolderSavedIN & "MacOSX/" & the cRevStandaloneSettings["name"] of this
stack & ".app" into tAppBundle
notarizeApp tAppbundle
else
put "Don't notarize"
end if
end if
pass standalonesaved
end standaloneSaved
on notarizeApp tAppbundle
put "Now notarizing..." &return &tAppBundle after message
##path to the notarizer Stack..
## either use an absolute path
--go stack "/Users/matthias/Dropbox/My
Livecode/Plugins/mrSignNotarizeHelperV2.livecode"
##or if the helper stack is in the plugins folder
go stack revEnvironmentUserPluginsPath()&"/mrSignNotarizeHelperV2.livecode"
put tAppbundle into fld "appbundle" of cd 1 of stack "mrSignNotarizeHelperV2"
set the label of btn "action" of cd 1 of stack "mrSignNotarizeHelperV2" to
"Codesign App, create & codesign DMG, then notarize DMG and staple DMG and App"
set the hilite of btn "debugmode" of cd 1 of stack "mrSignNotarizeHelperV2"
to false
send "mouseup" to btn "start" of cd 1 of stack "mrSignNotarizeHelperV2" in
5 seconds
end notarizeApp
-
Matthias Rebbe
Life Is Too Short For Boring Code
Am 13.04.2021 um 21:03 schrieb J. Landman Gay via use-livecode
<use-livecode@lists.runrev.com>:
On 4/13/21 10:43 AM, Keith Martin via use-livecode wrote:
On 13 Apr 2021, at 11:28, Andre Garzia via
use-livecode<use-livecode@lists.runrev.com> wrote:
On the other hand, I think that the SB should create standalones that can
actually be deployed, this means that it should be able to handle
notarisation on the mac out-of-the-box.
Oh boy, THIS!
+1. But for now I use Matthias' mrSignNotarize helper tool which makes the
process much easier. Fill out some info, click a button, and your
notarization request is sent to Apple, returned, and stapled to your app.
It's an extra step which I think LC should incorporate, but for now it
saves quite a bit of work. You can find it at this LC lesson, which
includes all the manual steps if you want to do it that way, but at the
bottom describes his automated tool as well. You can download the stack
from the link at the top of the lesson.
<https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore>
I've used it on more than one Mac app and it works. The hardest part is
dealing with Apple and of course there's no help for that.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.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
_______________________________________________
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
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.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
_______________________________________________
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
