Code-signed apk fails

panagiotis merakos merakosp at
Thu May 28 09:03:42 EDT 2020

Hello Jacque,

I did a quick test, I put this in a button:

get url "
put it into fld "url"

and signed the .apk with a release.keystore, and it works as expected for
me. The stack includes tsNet - I used LC 9.6 RC-2 for this.

Could you file a bug report with a recipe about this issue, and attach your
stack (or send it to me directly if it is confidential), so as we

Kind regards,

On Thu, 28 May 2020 at 14:41, JeeJeeStudio via use-livecode <
use-livecode at> wrote:

> The normal exstension is .keystore , maybe that's the reason?
> Op 28-5-2020 om 08:52 schreef J. Landman Gay via use-livecode:
> > We're about to release an Android app. I've been signing it for
> > development only and it works well. Today I created a keystore
> > "FPMobile.jks" in Terminal as usual.
> >
> > As an aside, I got this in Terminal:
> > Warning:
> > The JKS keystore uses a proprietary format. It is recommended to
> > migrate to PKCS12 which is an industry standard format using "keytool
> > -importkeystore -srckeystore FPMobile.jks -destkeystore FPMobile.jks
> > -deststoretype pkcs12".
> >
> > I don't know if that's significant. I've ignored it in the past, so I
> > went ahead and entered the jks file in standalone settings. When LC
> > 9.6rc2 asked me to locate the keystore during the build, I was unable
> > to select it in the file dialog until I chose "All files". That seemed
> > to work and the build finished.
> >
> > At any rate the real problem:
> >
> > The codesigned app fails to download files from the server. My error
> > log shows that sometimes there is no error at all but nothing is
> > downloaded, other times the error is vague: "Invalid URL:" with no URL
> > indicated. The same script and URLs work in the IDE and in the apk
> > when built without the keystore.
> >
> > I don't think codesigning should affect server queries but that seems
> > to be what's happening. I rebuilt the apk without any changes except
> > to remove the keystore and it worked perfectly again. Could TSNet be
> > involved somehow?
> >
> > I'm not sure where to look for the fault. Ideas?
> >
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the use-livecode mailing list