Error when creating Android standalone | DESPERATION!
    Klaus major-k 
    klaus at major-k.de
       
    Wed Oct 15 05:20:19 EDT 2025
    
    
  
Hi Panos,
> Am 15.10.2025 um 09:56 schrieb panagiotis merakos via use-livecode <use-livecode at lists.runrev.com>:
> 
> Hello Klaus,
> 
> Have you reached the point where it asks you for your alias and keystore
> passwords? Or is the error thrown before reaching this point?
after adding the breakpoint I got to the point where I entered keystore alias 
and passwords and wharnot!? WTF?
> Here is what you can do that _might_ provide some more information.
> Open the message box and type:
> put true into gRevDevelopment
> This will cause any breakpoints in the IDE stacks to be respected. Now time
> to add a breakpoint and see what happens line by line and where it fails.
> Type in the message box:
> edit the script of stack "revSaveAsAndroidStandalone"
> This will open the script editor at the script of this stack. Now scroll
> down to line 1389 and add a breakpoint at the beginning of this block:
I added this right before this block at line 1389:
...
    #### KM
    put the result
    breakpoint
if the result begins with "jarsigner error" then
   throw "signing failed -" && word 4 to -1 of the result
...
the result:
jarsigner error: java.lang.RuntimeException: keystore load: Invalid keystore format
Then everything went on in the script without problem and produced an .AAB file. 
But obviously UNSIGNED.
> if the result begins with "jarsigner error" then
>    throw "signing failed -" && word 4 to -1 of the result
> else if the result begins with "jarsigner: Certificate chain not found" then
>    throw "signing failed -" && word 2 to -1 of the result
> else if (the result begins with "jarsigner: key associated with") and (line
> 1 of the result ends with "not a private key") then
>    throw "signing failed - key password was incorrect or" && word 2 to -1
> of the result
> end if
> 
> Now build an Android standalone - this breakpoint should be hit. If not,
> try putting the breakpoint sooner in the handler. Once the breakpoint is
> hit, step over line by line to see where it fails, and what is the value of
> the various variables at this point.
> ...
> Hope this helps
> Panos
Best
Klaus
--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
klaus at major-k.de
    
    
More information about the use-livecode
mailing list