Sergio C.
09/22/2019, 9:08 PMdebugimplementation = "com.squareup.leakcanary:leakcanary-android:$Versions.leakCanary"
pvasa
09/22/2019, 9:12 PMdebugImplementation("com.squareup.leakcanary:leakcanary-android:${Versions.leakCanary}")
Sergio C.
09/22/2019, 9:20 PMSergio C.
09/22/2019, 9:21 PMSergio C.
09/22/2019, 9:22 PMlouiscad
09/22/2019, 9:27 PMVersions
written in a Groovy based gradle script?Sergio C.
09/22/2019, 9:28 PMSergio C.
09/22/2019, 9:28 PMSergio C.
09/22/2019, 9:29 PMSergio C.
09/22/2019, 9:29 PMSergio C.
09/22/2019, 9:31 PMandroid
is not resolving?Sergio C.
09/22/2019, 9:45 PMlouiscad
09/22/2019, 11:14 PMandroid
you're talking about exactly in which context, I only realize what it could be now.
So, I assume you mean android { … }
in the build.gradle.kts
file. I had it in red very very often on Android Studio 3.5 and before, but I'm no longer seeing the issue in Android Studio 3.6, so I can only encourage you to keep using Android Gradle plugin 3.5.0 but open the project with 3.6 Canary, you'll very likely get a better experience.gildor
09/23/2019, 12:47 AMandroid
and all other type-safe accessors if you use plugins DSL to apply pluginsSergio C.
09/23/2019, 12:00 PMandroid { … }
block in the build.gradle.kts
Well this took a while to debug. I found out that if you have some error somewhere else in the script that error might not get highlighted by the IDE but android block and everything inside is in screaming error red! ooohh ok then!Sergio C.
09/23/2019, 12:01 PMgildor
09/23/2019, 2:20 PM