Error: '@local_config_cc//:toolchain' does not contain a toolchain for cpu 'x86_64' about rules_android HOT 10 CLOSED

If people are still running into this, I'd suggest upgrading Bazel versions to 6.0.0 or higher and seeing if the problem persists, and if you're using a newer NDK version, to use https://github.com/bazelbuild/rules_android_ndk in place of the native android_ndk_repository.

I think it would be prudent to close out this bug, since there seem to be multiple solutions/workarounds, and little activity in this thread. I'll circle back in a week and close this out if there are no objections.

from rules_android.

Downgrading/upgrading the bazel verion (via bazelisk) didn't work.

from rules_android.

It is possible AS is using different bazel version. Have you configured the bazel binary path in AS settings to use bazelisk?

from rules_android.

i changed the bazel binary location to point to bazelisk, and it still gives the error :(

from rules_android.

Also worth running clean ——expunge to force toolchain resolution to run again.

from rules_android.

Tried clean --expunge as well, it didn't really help.
I'm fairly new to bazel, so at this point I wasn't sure how to proceed.

from rules_android.

If you're still running into this problem, and if your app has native dependencies (e.g. cc_library), it might be that there needs to be an android_ndk_repository rule in your WORKSPACE file:

android_ndk_repository(
  name = "androidndk",
)

and set the ANDROID_NDK_HOME environment variable to the path of a locally installed NDK (up to r21 is supported, see bazelbuild/bazel#12889)

from rules_android.

@snazhmudinov Still running into this issue?

from rules_android.

Not OP but I was able to resolve the issues by using r25 for the ndk instead of r21

from rules_android.

Sorry for the silence. I will check with the new bazel version. Meanwhile I'm closing this issue. Thank you!

from rules_android.