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
Hybrid build used to work on many heuristic assumptions especially with target names and that has since changed since we added android variant specific targets in Bazel. Due to this name change, dependency substitution no longer work correctly and probably needs review on how to link bazel built artifacts for Gradle use considering recent changes.
A proper approach might be to handle this in bazel-common similar to how databinding aar was handled and reduce the implementation details in grazel for scalability.
The text was updated successfully, but these errors were encountered:
Hybrid build used to work on many heuristic assumptions especially with target names and that has since changed since we added android variant specific targets in Bazel. Due to this name change, dependency substitution no longer work correctly and probably needs review on how to link bazel built artifacts for Gradle use considering recent changes.
A proper approach might be to handle this in bazel-common similar to how databinding aar was handled and reduce the implementation details in grazel for scalability.
The text was updated successfully, but these errors were encountered: