Gradle error building Androwish tcl apk

Hello,
First time here. Hope I’m in the right place. Clueless…
I build an apk of my little tcl/tk app years ago. Trying to update it but I no longer have that build environment.
Androwish SDK: C:\android\AWSDK
Android studio command line tools: C:\android\ASSDK - which is how ANDROID_HOME is set.
When I run bones and it invokes gradle, it errors out as below - looking for a concatenation of both paths, with the “\” removed from the ANDROID_HOME path.
I’m just a hobby-shop guy fiddling with tcl/tk. My app is a Kanji “flash card” app: Kanji Quiz – 漢字クイズ | GeezBlog
Totally at sea here, and grateful for any help.
thanks, Bill

...................................................
Starting a Gradle Daemon, 2 incompatible and 1 stopped Daemons could not be reused, use --status for details

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'AndroWishApp'.
> The SDK directory 'C:\android\AWSDK\C:androidASSDK' does not exist.

Did you follow the advice in the error message?
If not, why not?
If yes, why do you not provide the additional information, especially --stracktrace or optimally build --scan URL?

I don’t know where to find gradle in order to launch with options. I’m using the Androwish tools and the closest I can find is a jar wrapper.
I apologize for not providing much information. I’m totally lost here. If I’m too hopless to help I will withdraw my question.
Bill

I don’t even know what Androwish is.
But from the given information it is impossible to say aything meaningful, at least for me.

Thank you and sorry for your trouble. I found and can run gradlew.bat with options but all my attempts to capture the output to a file end in an empty file. I’m stuck on the simplest things…
Bill

Well, as I you do not share anything about your environment or what you tried, I can hardly say anything to that, besides that it is off-topic most probably anyway as this is a forum about Gradle, not how to use the commandline. :slight_smile:
But if you would use a build --scan as recommended you could easily share your output without any file redirection.

My friend, I don’t share anything because I’m a first-timer and don’t know how. This, perhaps:
https://scans.gradle.com/s/zzhdtt6t4l5qk
[edit to add] it seems to show that same mashed-up path. Can you tell if this is something gradle is doing, or a messed-up parameter being passed to it?
thanks
Bill

Don’t use backslashes in values of local.properties.
A properties file is not pure text, it has rules.
A backslash escapes the next character.
So either use forward slashes, or double the backslashes.

Thanks. I don’t use backslashes anywhere. I haven’t touched local.properties. This is all from running an Androwish build tool called bones. The only things I’ve touched are JAVA_HOME an ANDROID_HOME in env variables.

I will go look at local.properties and see what’s there.

The issue remains that bizarre path. It does in fact have a missing backslash, but wouldn’t make any sense even if it was there.

1 Like

You can see in the build scan that the message is coming from that ancient Android Gradle Plugin you are using and there it is when finding the sdk path, which takes paths from local properties usually. And as you get the same error when running from commandline to produce that build scan, I assume that bones tool is not related to your problem. If you don’t have the paths in local properties, then check your environment variables, maybe you have set them to wrong values.

1 Like

May I ask you to check the sdk.dir=... value that resides in the local.properties file and test whether this location is accessible on your system?

AGP cannot operate on your source code without accessing the Android SDK Tools.