Android Keystore signing problem

scott at elementarysoftware.com scott at elementarysoftware.com
Mon Dec 21 17:09:40 EST 2020


Thanks Ralph!


> On Dec 21, 2020, at 7:24 AM, Ralph DiMola via use-livecode <use-livecode at 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
> rdimola at evergreeninfo.net
> 
> 
> -----Original Message-----
> From: use-livecode [mailto:use-livecode-bounces at 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 | jacque at hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On December 20, 2020 7:07:05 PM scott--- via use-livecode <use-livecode at lists.runrev.com> 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: <my keystore alias>.    
>> <my keystore alias> must reference a valid KeyStore key entry 
>> containing a private key and corresponding public key certifcate chain."
>> 
>> (Where <my keystore alias> 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     scott at elementarysoftware.com
>> booth    1-360-734-4701
>> ------------------------------------------------------
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> 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
> 
> 
> _______________________________________________
> 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





More information about the use-livecode mailing list