Re: Android Keystore signing problem

[panagiotis merakos via use-livecode]

Hello Scott,

When adding breakpoints in IDE scripts, you also need to do (in the msg
box):

put true into gRevDevelopment

otherwise breakpoints won't be respected.

Kind regards,
Panos
--

On Tue, 22 Dec 2020 at 02:20, scott--- via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hello All,
>
> I used edit the script of stack “revSaveAsAndroidStandalone”in the
> message box and  tried putting a breakpoint in at that spot (and several
> others) but it isn’t triggering.   This inside the handler:
>
> private command revSaveAsMobileStandaloneMain
>
> I’m not sure that I’ve ever done more than examine LC scripts. Is there
> something else I need to know in order to get the debugger to open on a
> breakpoint with them? (Script Debug Mode is checked :- )
>
> I’ve restarted the computer and tried a couple different versions of
> Livecode… feeling even more clueless than usual.
>
> —
> Scott
>
> > On Dec 21, 2020, at 7:24 AM, Ralph DiMola via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Scott.
> >
> > I looked at the source of stack "revSaveAsAndroidStandalone" and it
> looks like it failed at line 1067 or 1069 (9.6.1). As JLM said this appears
> that the keystore your referencing does not hold the alias your entering.
> Everything after "There was an error while saving the standalone
> application signing failed-" is coming from the jar signer(but only word 4
> to -1). You can put in a breakpoint at 1065 and examine the full result of
> the shell to jar signer.
> >
> > Ralph DiMola
> > IT Director
> > Evergreen Information Services
> > rdim...@evergreeninfo.net
> >
> >
> > -Original Message-
> > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf Of J. Landman Gay via use-livecode
> > Sent: Sunday, December 20, 2020 11:18 PM
> > To: How to use LiveCode
> > Cc: J. Landman Gay
> > Subject: Re: Android Keystore signing problem
> >
> > If it was working before then it should still work now. Check the
> Android settings and make sure that the path to the file is correct. The
> error sounds like LC can't find it.
> >
> > --
> > Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software
> | http://www.hyperactivesw.com On December 20, 2020 7:07:05 PM scott---
> via use-livecode  wrote:
> >
> >> When trying to create an update for an app on Google Play I am getting
> >> this message when attempting to create the standalone .apk.
> >>
> >> "There was an error while saving the standalone application
> >> signing failed - Certificate chain not found for: .
>
> >>  must reference a valid KeyStore key entry
> >> containing a private key and corresponding public key certifcate chain."
> >>
> >> (Where  is actually my keystore alias.)
> >>
> >> This is the same keystore file that I have used in the past. My
> >> understanding (and failed attempts) indicate that creating a new
> >> keystore file won’t work if I’m using it to update an existing app on
> the Play Store.
> >> I’m quite inexperienced with android builds. Any suggestions would be
> >> most welcome as I’ve about run out of ideas (and Google search
> >> queries.)
> >>
> >> --
> >> Scott Morrow
> >>
> >> Elementary Software
> >> (Now with 20% less chalk dust!)
> >> web   https://elementarysoftware.com/
> >> email sc...@elementarysoftware.com
> >> booth1-360-734-4701
> >> --
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> 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: Android Keystore signing problem

[scott--- via use-livecode]

Hello All,

I used edit the script of stack “revSaveAsAndroidStandalone”in the 
message box and  tried putting a breakpoint in at that spot (and several 
others) but it isn’t triggering.   This inside the handler:

private command revSaveAsMobileStandaloneMain

I’m not sure that I’ve ever done more than examine LC scripts. Is there 
something else I need to know in order to get the debugger to open on a 
breakpoint with them? (Script Debug Mode is checked :- )

I’ve restarted the computer and tried a couple different versions of Livecode… 
feeling even more clueless than usual.

— 
Scott

> On Dec 21, 2020, at 7:24 AM, Ralph DiMola via use-livecode 
>  wrote:
> 
> Scott.
> 
> I looked at the source of stack "revSaveAsAndroidStandalone" and it looks 
> like it failed at line 1067 or 1069 (9.6.1). As JLM said this appears that 
> the keystore your referencing does not hold the alias your entering. 
> Everything after "There was an error while saving the standalone application 
> signing failed-" is coming from the jar signer(but only word 4 to -1). You 
> can put in a breakpoint at 1065 and examine the full result of the shell to 
> jar signer.
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> 
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf 
> Of J. Landman Gay via use-livecode
> Sent: Sunday, December 20, 2020 11:18 PM
> To: How to use LiveCode
> Cc: J. Landman Gay
> Subject: Re: Android Keystore signing problem
> 
> If it was working before then it should still work now. Check the Android 
> settings and make sure that the path to the file is correct. The error sounds 
> like LC can't find it.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | 
> http://www.hyperactivesw.com On December 20, 2020 7:07:05 PM scott--- via 
> use-livecode  wrote:
> 
>> When trying to create an update for an app on Google Play I am getting 
>> this message when attempting to create the standalone .apk.
>> 
>> "There was an error while saving the standalone application
>> signing failed - Certificate chain not found for: .
>>  must reference a valid KeyStore key entry 
>> containing a private key and corresponding public key certifcate chain."
>> 
>> (Where  is actually my keystore alias.)
>> 
>> This is the same keystore file that I have used in the past. My 
>> understanding (and failed attempts) indicate that creating a new 
>> keystore file won’t work if I’m using it to update an existing app on the 
>> Play Store.
>> I’m quite inexperienced with android builds. Any suggestions would be 
>> most welcome as I’ve about run out of ideas (and Google search 
>> queries.)
>> 
>> --
>> Scott Morrow
>> 
>> Elementary Software
>> (Now with 20% less chalk dust!)
>> web   https://elementarysoftware.com/
>> email sc...@elementarysoftware.com
>> booth1-360-734-4701
>> --
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> 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: Android Keystore signing problem

[scott--- via use-livecode]

Thanks Ralph!


> On Dec 21, 2020, at 7:24 AM, Ralph DiMola via use-livecode 
>  wrote:
> 
> Scott.
> 
> I looked at the source of stack "revSaveAsAndroidStandalone" and it looks 
> like it failed at line 1067 or 1069 (9.6.1). As JLM said this appears that 
> the keystore your referencing does not hold the alias your entering. 
> Everything after "There was an error while saving the standalone application 
> signing failed-" is coming from the jar signer(but only word 4 to -1). You 
> can put in a breakpoint at 1065 and examine the full result of the shell to 
> jar signer.
> 
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> 
> 
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf 
> Of J. Landman Gay via use-livecode
> Sent: Sunday, December 20, 2020 11:18 PM
> To: How to use LiveCode
> Cc: J. Landman Gay
> Subject: Re: Android Keystore signing problem
> 
> If it was working before then it should still work now. Check the Android 
> settings and make sure that the path to the file is correct. The error sounds 
> like LC can't find it.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | 
> http://www.hyperactivesw.com On December 20, 2020 7:07:05 PM scott--- via 
> use-livecode  wrote:
> 
>> When trying to create an update for an app on Google Play I am getting 
>> this message when attempting to create the standalone .apk.
>> 
>> "There was an error while saving the standalone application
>> signing failed - Certificate chain not found for: .
>>  must reference a valid KeyStore key entry 
>> containing a private key and corresponding public key certifcate chain."
>> 
>> (Where  is actually my keystore alias.)
>> 
>> This is the same keystore file that I have used in the past. My 
>> understanding (and failed attempts) indicate that creating a new 
>> keystore file won’t work if I’m using it to update an existing app on the 
>> Play Store.
>> I’m quite inexperienced with android builds. Any suggestions would be 
>> most welcome as I’ve about run out of ideas (and Google search 
>> queries.)
>> 
>> --
>> Scott Morrow
>> 
>> Elementary Software
>> (Now with 20% less chalk dust!)
>> web   https://elementarysoftware.com/
>> email sc...@elementarysoftware.com
>> booth1-360-734-4701
>> --
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ___
>> 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

[ANN] This Week in LiveCode 249

[panagiotis merakos via use-livecode]

Hi all,

Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!

Read issue #249 here: http://bit.ly/3pgIHuq

This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around the open source project. New issues will be
released weekly on Mondays. We have a dedicated mailing list that will
deliver each issue directly to your e-mail, so you don't miss any!

If you have anything you'd like mentioned (a project, a discussion
somewhere, an upcoming event) then please get in touch.

-- 
Panagiotis Merakos 
LiveCode Software Developer

Everyone Can Create Apps 
___
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: Android Keystore signing problem

[Ralph DiMola via use-livecode]

Scott.

I looked at the source of stack "revSaveAsAndroidStandalone" and it looks like 
it failed at line 1067 or 1069 (9.6.1). As JLM said this appears that the 
keystore your referencing does not hold the alias your entering. Everything 
after "There was an error while saving the standalone application signing 
failed-" is coming from the jar signer(but only word 4 to -1). You can put in a 
breakpoint at 1065 and examine the full result of the shell to jar signer.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of 
J. Landman Gay via use-livecode
Sent: Sunday, December 20, 2020 11:18 PM
To: How to use LiveCode
Cc: J. Landman Gay
Subject: Re: Android Keystore signing problem

If it was working before then it should still work now. Check the Android 
settings and make sure that the path to the file is correct. The error sounds 
like LC can't find it.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | 
http://www.hyperactivesw.com On December 20, 2020 7:07:05 PM scott--- via 
use-livecode  wrote:

> When trying to create an update for an app on Google Play I am getting 
> this message when attempting to create the standalone .apk.
>
> "There was an error while saving the standalone application
> signing failed - Certificate chain not found for: .
>  must reference a valid KeyStore key entry 
> containing a private key and corresponding public key certifcate chain."
>
> (Where  is actually my keystore alias.)
>
> This is the same keystore file that I have used in the past. My 
> understanding (and failed attempts) indicate that creating a new 
> keystore file won’t work if I’m using it to update an existing app on the 
> Play Store.
> I’m quite inexperienced with android builds. Any suggestions would be 
> most welcome as I’ve about run out of ideas (and Google search 
> queries.)
>
> --
> Scott Morrow
>
> Elementary Software
> (Now with 20% less chalk dust!)
> web   https://elementarysoftware.com/
> email sc...@elementarysoftware.com
> booth1-360-734-4701
> --
>
>
>
>
>
>
>
>
> ___
> 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