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. execute dispatch "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 <https://livecode.com/docs/9-5-0/faq/faq/> 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 > <use-livecode@lists.runrev.com>: > > 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
