Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 558956]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
From what I see, the dependency cycle
:app:compileDebugKotlin
+--- :app:dataBindingExportBuildInfoDebug
\--- :app:compileDebugKotlin (*)
is caused by compileDebugKotlin being registered as a bytecode producer and a Java sources consumer, and dataBindingExportBuildInfoDebug, in turn, consuming the bytecode from compile classpath and producing the sources. I don't see a simple solution from our side, and, probably, it requires a fix in the Android plugin, like excluding the registered external bytecode from the classpath for Data Binding, or adding some special logic to determine which of the bytecode generators use the sources (or registering them as such).