subject:"Code\-signed apk fails"

Re: Code-signed apk fails

2020-05-28 Thread matthias rebbe via use-livecode

Good to hear that you´ve found the solution.



-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 28.05.2020 um 20:24 schrieb J. Landman Gay via use-livecode 
> :
> 
> Okay, here are the results of my tests, all done in LC 9.6rc2.
> 
> 1. Keystore: FPMobile.jks, included TSNet: fails to download files
> 2. Keystore: FPMobile.jks, TSNet removed: works
> 3. Keystore: FPMobile.keystore, included TSNet: works
> 
> So TSNet doesn't like "jks" extensions, which is the file extension Google 
> suggests. But I am baffled why a keystore would affect TSNet at all, not to 
> mention it only prevents file downloads. The user can log in normally, make 
> php queries to the server and get replies, the only thing that fails is 
> actually downloading files.
> 
> Panos, is this bug-worthy? Or is it a documentation thing?
> 
> 
> On 5/28/20 8:03 AM, panagiotis merakos via use-livecode wrote:
>> Hello Jacque,
>> I did a quick test, I put this in a button:
>> get url "https://google.com
>> "
>> 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
>> investigate?
>> Kind regards,
>> Panos
>> --
> 
> 
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com 
> 
> HyperActive Software   | http://www.hyperactivesw.com 
> 
> 
> ___
> 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: Code-signed apk fails

2020-05-28 Thread J. Landman Gay via use-livecode


Okay, here are the results of my tests, all done in LC 9.6rc2.

1. Keystore: FPMobile.jks, included TSNet: fails to download files
2. Keystore: FPMobile.jks, TSNet removed: works
3. Keystore: FPMobile.keystore, included TSNet: works

So TSNet doesn't like "jks" extensions, which is the file extension Google suggests. But I am 
baffled why a keystore would affect TSNet at all, not to mention it only prevents file 
downloads. The user can log in normally, make php queries to the server and get replies, the 
only thing that fails is actually downloading files.


Panos, is this bug-worthy? Or is it a documentation thing?


On 5/28/20 8:03 AM, panagiotis merakos via use-livecode wrote:

Hello Jacque,

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

get url "https://google.com
"
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
investigate?

Kind regards,
Panos
--





--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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: Code-signed apk fails

2020-05-28 Thread J. Landman Gay via use-livecode

I'm fairly sure that's the reason the file dialog didn't enable the .jks file, but the file
still works. I used Google's terminal command example, which creates .jks files, instead of
LC's example which I think uses .keystore. Next time I'll change the extension just to make
file selection easier.

On 5/28/20 6:40 AM, JeeJeeStudio via use-livecode 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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com

Re: Code-signed apk fails

2020-05-28 Thread J. Landman Gay via use-livecode


On 5/28/20 5:24 AM, matthias rebbe via use-livecode wrote:

did you already try to build the .apk without tsNet?  This way you could check 
if tsNET is involved.
You need to do the 2 steps before building the .apk
1. executedispatch "revUnloadLibrary" to stack "tsNetLibUrl"in message 
box
(btw. to load it again after building the standalone execute dispatch 
"revLoadLibrary" to stack "tsNetLibUrl" - no need to restart LC IDE )
2. if "Select inclusions for..." is selected, then deselect tsNET external in 
standalone settings.

Now build the .apk with the keystore.
If the .apk is able now to download the files although it is signed, then tsNET 
is involved.


I did this. Without TSNet, the apk works perfectly again. Now I wonder if I can do without 
TSNet for now.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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: Code-signed apk fails

2020-05-28 Thread panagiotis merakos via use-livecode

Hello Jacque,

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

get url "https://google.com
"
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
investigate?

Kind regards,
Panos
--



On Thu, 28 May 2020 at 14:41, JeeJeeStudio via use-livecode <
use-livecode@lists.runrev.com> 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@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: Code-signed apk fails

2020-05-28 Thread JeeJeeStudio via use-livecode


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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Code-signed apk fails

2020-05-28 Thread matthias rebbe via use-livecode

Jacque,

did you already try to build the .apk without tsNet?  This way you could check 
if tsNET is involved.
You need to do the 2 steps before building the .apk
1. executedispatch "revUnloadLibrary" to stack "tsNetLibUrl"in message 
box
(btw. to load it again after building the standalone execute dispatch 
"revLoadLibrary" to stack "tsNetLibUrl" - no need to restart LC IDE )
2. if "Select inclusions for..." is selected, then deselect tsNET external in 
standalone settings.

Now build the .apk with the keystore.
If the .apk is able now to download the files although it is signed, then tsNET 
is involved.

If the .apk still does not download, then i would try to convert the keystore 
file to the new format as suggested in the warning message and would try to use 
that file during standalone building.


And if you are on Mac and if your time allows could you try an older LC version 
to build the .apk. e.g. 9.6.0 DP3. According to the FAQ at Livecode.com 

all DP versions are not notarized:
"Our test releases (DP versions) will not be fully notarized and you will still 
need to do this. Future Stable releases will be notarized and will not need 
whitelisting."

So RC1 and RC2 could be notarized and who knows, if or if not  the notarization 
process touched the Android externals of tsNET in some way. But that´s just a 
shot in the dark.


Matthias




-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 28.05.2020 um 08:52 schrieb 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?
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
> 
> ___
> 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

Code-signed apk fails

2020-05-28 Thread 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:

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?

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com

Re: Code-signed apk fails

Re: Code-signed apk fails

Re: Code-signed apk fails

Re: Code-signed apk fails

Re: Code-signed apk fails

Re: Code-signed apk fails

Re: Code-signed apk fails

Code-signed apk fails

8 matches

Site Navigation

Mail list logo

Footer information