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
This may be related to #9. Our setup is a multi-project Gradle build, where multiple Android application projects depend on a common Android library project (which we want to use leakcanary to verify leaks).
Forcing Gradle Android plugin to publish library as 'debug' of course works, but that would affect our 'release' setup.
android {
defaultPublishConfig "debug"
}
Another workaround would be to always compile leakcanary-android, and then exclude leakcanary logic based on some build type specific configuration during runtime, but that would defeat the purpose of having leakcanary-android-no-op.
This may be related to #9. Our setup is a multi-project Gradle build, where multiple Android application projects depend on a common Android library project (which we want to use leakcanary to verify leaks).
I was trying to add leakcanary to a library project when I realized that Gradle only builds release variant of library projects, which is a known Gradle Android plugin issue, which means
leakcanary-android-no-op
would be built instead ofleakcanary-android
if we include leakcanary in our library project as follows:Forcing Gradle Android plugin to publish library as 'debug' of course works, but that would affect our 'release' setup.
android { defaultPublishConfig "debug" }
Another workaround would be to always compile
leakcanary-android
, and then exclude leakcanary logic based on some build type specific configuration during runtime, but that would defeat the purpose of havingleakcanary-android-no-op
.Have anyone encountered the same problem? Any other workarounds?
The text was updated successfully, but these errors were encountered: