Page 2 of 2
Re: Mobile support
Posted: Mon Sep 08, 2025 1:58 pm
by Klaus
For your interest, Panos answer to my question on the mailing-list:
----------------------------------------------------------------------
...
We have a new lesson here:
https://lessons.livecode.com/m/4069/l/1 ... -and-later
In short, at least I have only tested this on mac -
you do not have to
uninstall Java 8 before installing a newer version. LiveCode should be
smart enough to pick the newest version.
Also no need to uninstall older versions of the build-tools - you just have
to ensure v34.0.0 or above is installed.
Also, as long as you have a JDK of version 11 or above installed, it should
make no difference whether this is v11.x or v24.x or anything in-between.
I have installed JDK v17 and it works as expected.
...
---------------------------------------------------------------------
Re: Mobile support
Posted: Thu Sep 11, 2025 12:43 pm
by jaui
Hello,
It's great that LiveCode is smart enough to select the latest version of Java, and the latest Android Studio Setup Checklist is also excellent. If it could now explain what to do when a JDK filepath is not reported underneath, that would be even greater.
jaui
Re: Mobile support
Posted: Thu Mar 12, 2026 6:46 am
by robertscott56
I had a similar issue on Windows 11 — make sure your JDK path doesn’t have spaces and points to the correct root folder (like C:\Program Files\Java\jdk-XX). Also check that JAVA_HOME is set correctly in your environment variables. Restart LiveCode after setting it, that helped in my case.
Re: Mobile support
Posted: Sun Apr 05, 2026 4:56 pm
by jaui
LC 10.0.4, Windows 11, Android Studio Panda, API 35, Java 11
Fed up! This is my chat with CLAUDE concerning these endless problems:
Nothing again! Now come up with something, or admit that you’re completely wrong or LiveCode is no good:
"I apologize; that was frustrating, and my suggestions didn’t work.
Let me be honest: The problem is probably that LiveCode 10.0.4 is fundamentally incompatible with Android Studio Panda—that’s a known issue that LiveCode itself needs to resolve.
Here’s what I recommend:
1. Post your problem directly on the LiveCode forum:
o
https://forums.livecode.com
o Category: “Android Deployment”
o Describe exactly: LC 10.0.4, Windows 11, Android Studio Panda, API 35, Java 11
There are developers there who can look directly into the LiveCode source code—this is a problem that’s beyond my capabilities.
Or: Wait for LiveCode 10.0.5—such compatibility issues are usually fixed in patch versions.
I’m sorry I couldn’t provide you with a working solution today!"
Happy Easter!!!!
Jaui
Re: Mobile support
Posted: Mon Apr 06, 2026 5:01 pm
by LiveCode_Panos
Hello Jaui,
What is the exact problem/error message you are seeing? Is it that the JDK path is not auto-populated? If so, have you tried Alice's suggestion, to enable the button chooseJDK and select the jdk path manually?
Kind regards,
Panos
--
Re: Mobile support
Posted: Mon Apr 13, 2026 4:06 pm
by jaui
Hi Panos,
yes I did and after changing Android Studio Panda to Narwhal it worked.
Thank you anyhow,
kind regards,
Jaui
Re: Mobile support
Posted: Sun May 03, 2026 11:47 am
by louis1
If you’re dealing with mobile support setup in LiveCode, the good news is you don’t need to overcomplicate things. Just make sure you have a JDK version 11 or higher installed (many people find Java Development Kit 17 works smoothly), and keep your Android build-tools updated to or above. You can leave older versions installed LiveCode usually picks the latest one automatically. In short, focus on updating rather than uninstalling, and you getthespikeapk should be good to go without issues
Re: Mobile support
Posted: Mon Jun 01, 2026 8:19 am
by suhusfa
I had the same problem on Windows 11. LiveCode detected my Android SDK, but the JDK path would not initialize correctly. In my case, the issue was caused by an incompatible Java version.
I fixed it by installing a supported JDK version and then manually selecting the JDK installation folder in LiveCode Preferences. After restarting LiveCode, the JDK path was recognized normally.
You should also check that both the SDK and JDK paths contain no invalid characters and that LiveCode has permission to access those folders. If you're using the latest JDK release, try switching to an older LTS version, as some versions of LiveCode don't work well with newer Java releases.