Android Studio LadyBug Fails to Find cargo

[Archdoog]

willir/cargo-ndk-android-gradle#24

[ianthetechie]

Weird. I had reports of similar issues from another user on Windows several weeks ago with a much older version of Android Studio. They eventually solved it but I never quite got out of them what the root cause was / how they fixed it. Not sure if this is the same though, since in their case it was usually errors about the NDK not being found rather than cargo itself.

Random idea: I know JetBrains IDEs are really funky with the way they execute your shell and get path info from it at launch. I have experienced issues in the past with my shell (fish + starship + a few other things) hanging and screwing up an entire IDE session in other JetBrains products. I assume you've done a restart, but worth asking...

[Archdoog]

This looks interesting: https://github.com/mozilla/rust-android-gradle.

[Archdoog]

Still haven't figured it out 🙃. Update: willir/cargo-ndk-android-gradle#24 (comment).

[ianthetechie]

This looks interesting: https://github.com/mozilla/rust-android-gradle.

This project used to use that actually, but switched to the current setup after several issues. You might find this comment in particular interesting (not in a technical/solution sense, but in why I ultimately went with willr's solution instead): mozilla/rust-android-gradle#40 (comment).

[Archdoog]

Workaround on MacOS is to open android studio using open -na "Android Studio" from terminal.

[ahmedre]

2 things I noticed -

1. I had this happen on the command line also, so I don't think it's Android Studio specific (it shows the correct path, including where cargo lives)
2. killing Gradle daemons fixes it for me , without restarting Android Studio - i.e. ./gradlew --stop and then rebuilding on command line works (even if it was failing on command line as per point 1), and then going back to Android Studio and building works from then on.

[Archdoog]

Here's the Android Studio issue ticket: https://issuetracker.google.com/issues/377339196. Feel free to vote "I am impacted" on top right.

[ahmedre]

It's not Android Studio specific though -

I got out of this by just doing ./gradlew --stop - building (both on command line and in the IDE) worked afterwards.

[ianthetechie]

Has anyone encountered this recently? I haven't heard any complaints in like 3 months.

[Archdoog]

It's still a problem. I just open android studio with open -na "Android Studio" for any ferrostar work 😆

[ianthetechie]

Quick update on this to confirm that it's still a bug. Further, it seems to be related to which JDK you use. @Archdoog put me on to this at some point but I forgot until working on #802 which required upgrading to JDK 21 and now I'm hitting the same issue 😂