Repository navigation
When are firebase_analytics, firebase_core, firebase_crashlytics and firebase_performance leaving KGP behind ? #18756
Replies: 1 comment
|
With AGP 9 and built-in Kotlin on, these plugins already don't apply KGP. The warning is coming from how Flutter detects it: it doesn't run the plugin's build script, it searches the text of // AGP 9+ has built-in Kotlin support unless Flutter opts out via android.builtInKotlin=false.
def agpMajor = com.android.Version.ANDROID_GRADLE_PLUGIN_VERSION.tokenize('.')[0] as int
def builtInKotlin = providers.gradleProperty("android.builtInKotlin")
.map { it.toBoolean() }
.orElse(agpMajor >= 9)
.get()
if (agpMajor < 9 || !builtInKotlin) {
apply plugin: 'kotlin-android'
}I ran Flutter's regex against the A maintainer explained the same thing here. The line is kept so AGP 8 and One thing to check on your side: android.builtInKotlin=falseIf you still have that, the condition above is true, and the Firebase plugins (and Flutter itself, for your app module) really do apply KGP. Once your app is migrated to built-in Kotlin (guide), set it to |
Uh oh!
There was an error while loading. Please reload this page.
I still get theese warnings, even I have moved to AGP for android.
When is it scheduled to leave KGP ?
All reactions