Error when creating Android standalone | DESPERATION!

[panagiotis merakos]

Hello Klaus,

Hmm, if you get that error message BEFORE the standalone builder asks you
to enter your alias, password etc, it sounds like LC thinks the path to
your keystore file is invalid. Could you empty the key field in the
standalone settings, and choose your key again?

Also, regarding the deadline, the message you received indeed means what
you said - i.e. that you have to submit an update before the 1st of Nov -
however it does not make much sense. This is the announcement from Google:

"Starting November 1st, 2025, all new apps and updates to existing apps
submitted to Google Play and targeting Android 15+ devices must support 16
KB page sizes on 64-bit devices."

https://developer.android.com/guide/practices/page-sizes

Anyway it would be good to resolve the signing problem anyway.

Kind regards,
Panos

On Wed, 15 Oct 2025 at 11:10, Klaus major-k via use-livecode <
use-livecode at lists.runrev.com> wrote:

> 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?
>
> before reaching that point.
>
> > 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:
> > 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.
>
> Thanks a bunch, will do that and report back.
>
> > Also, may I ask why your deadline is the 1st of November? If the issue is
> > the 16KB page size requirement, note that your app will NOT be removed if
> > you don't meet it. What this deadline means is that any new app or app
> > update that is submitted *after* the 1st of November must meet this
> > requirement. However, we will release a new version that supports this on
> > tsNet and PDF widget (since only these 2 components are affected now)
> > before the deadline anyway.
>
> I just had a look at the notifications in my Google dev account and it
> reads:
> ...
> If you want to publish any further updates of your app you need
> to recompile it to support the 16 KB requirement. until november 1st.
> ...
> So we probably intend to create an update at some point, I think I have to
> update our app. Not?
>
> > Hope this helps
> > Panos
> > --
>
> Best
>
> Klaus
>
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> klaus at major-k.de
>
>
> _______________________________________________
> 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
>