LiveCode Forums.

Sparkout. I don't know if that reply was to me but SDK Build tool is 31.0 and only that one.

Any ideas?

I have the same problem: I have followed the steps outlined in this LiveCode lesson: https://lessons.livecode.com/a/1770871- ... -checklist

I can see all the expected directories that the lesson says I should see, but when I try to set the SDK root path in LC it tells me "The chosen folder is not a valid Android SDK. Please ensure you have installed it correctly, and enabled support for 14 (API 34)"

I'm stumped. :-/

Do you have Java 8 and only Java 8 installed?

Best Regards,

Heather

Yes, as per the LiveCode lesson (https://lessons.livecode.com/a/1770871- ... -checklist) I installed JDK8 and now have this: /Library/Java/JavaVirtualMachines/jdk-1.8.jdk

There's no other Java installation that I know of or can find on this Mac. (I'm sure there isn't but I looked around anyway.)

Oddly, when I launch Android Studio I get this notice: But when I look in the SDK manager I see this:

After poking deeper and cross-referencing with the LiveCode lesson, AND going for Android 14 ("UpsideDownCake") instead of 13 (and getting past the confusion of the Android API 34 reference), I got LiveCode to accept the SDK path.

Next hurdle: I have "Signing: Do not sign" set for this stack, but the build process ends with a message about signing failing:

There was an error while saving the standalone application
signing failed - keystore load: Invalid keystore format

Given that the Standalone Application Settings specifically say 'do not sign' is this a hiccup? I'm using 10.0.1 (rc3).

k

Hi Keith,

ouch, I have the same problem with a VALID keystore file, but with: Android Studio Iguana | 2023.2.1 Patch 1
I also get this message:
There was an error while saving the standalone application
signing failed - keystore load: Invalid keystore format

I know that the key is valid, since last year Matthias Rebbe was so kind to create an
android runtime for me with exactly that same key!?

So I guess this might be a problem with LC?
I will ask the mailing list, maybe someone can take a looke here and can help.

Edit: DONE!

Best
Klaus

Hello all,

The "Do not Sign" option has a bug - instead you can choose either "Sign for Development only" or "Sign with my key" and choose a valid keystone file in this case.

Kind regards,
Panos
--

Hi Panos,

thank you for taking a look here!

But what could cause my problem WITH a valid keystore file?
I use "Sign with my key" and LC does show the mentioned error, the key IS in fact valid!


Best

Klaus

Hello Klaus,

Hmm, not sure TBH! I have not encountered this issue.

I would only suggest you type your keystore passwords very slowly, since if you type fast some keystrokes are missed (and thus the password typed is incorrect).

Also, how did you create your .keystore file? Did you follow this lesson, specifically the part "How to create a certificate using Android Studio" here:

https://lessons.livecode.com/m/4069/l/3 ... ndroid-app

Kind regards,
Panos
--

Hi Panos,

well I quadruple-checked the passwords etc. and even copied them from a text file, they are in fact correct.

Remember the big problems I had last autumn with creating that keystore file?
Anyway, Matthias R. used exactly that namely keystore file to kindly and successfully created a runtime
for me last year that I could successfully upload to the Google dev account.

I could send you the key file via private email for testing if you'd like to check.
I'm completely lost...

Best

Klaus

Do you happen to know the correct ORDER of the dialogs, see below, where you enter alias name and password and whatnot for the keystore file?
So I can exclude this as the source of my inconvenience, thank you!

?. password for Keystore file
?. aliasname for key
?. password for key