You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error in fail: Dependencies on .jar artifacts are not allowed in Android binaries, please use a java_import to depend on apps/rider/libsrc_devDebug.jar. If this is an implicit dependency then the rule that introduces it will need to be fixed to account for it correctly.
I did some debugging to try to narrow this one down. It seems that the transitions are correctly being applied when the aspect executes, but when the Android binary calls into _to_dexed_classpath it fails to find the accompanying aspect outputs for the given transition.
The text was updated successfully, but these errors were encountered:
Yes it looks like one part of the code is looking through jars from one configuration, and trying to look up those same jars in a dict formed from jars in a another configuration.
even though libbasic_lib.jar is in the dict, it's from a different configuration (k8-fastbuild-android-ST-a9ac79439181, k8-fastbuild-android-ST-9b738726d3a8). Interestingly this does not appear to happen internally (i.e. with multiple values to --android_platforms)....
Steps to reproduce:
cd
intoexamples/basicapp/
USE_BAZEL_VERSION=last_green bazel build //... --android_platforms=@rules_android//:armeabi-v7a,@rules_android//:arm64-v8a --enable_bzlmod=true
The above will produce the following error:
I did some debugging to try to narrow this one down. It seems that the transitions are correctly being applied when the aspect executes, but when the Android binary calls into
_to_dexed_classpath
it fails to find the accompanying aspect outputs for the given transition.The text was updated successfully, but these errors were encountered: