The Android Gradle plugin supports only Kotlin Gradle plugin version 1.5.20 and higher. about dart_packages

[tp]

@MuhammadWaqar340 What version of the plug-in are you using (in your pubspec.lock file)?

We are currently using kotlin-gradle-plugin version 1.7.10, so it looks to me like you're using an older version and could just upgrade to solve this issue.

[MuhammadWaqar340]

@tp Kindly guide me how do i upgrade kotlin-gradle-plugin version ?

plugins {
id "dev.flutter.flutter-plugin-loader" version "1.0.0"
id "com.android.application" version "7.3.0" apply false
id "org.jetbrains.kotlin.android" version "1.9.0" apply false
}

[tp]

@MuhammadWaqar340 I don't think that's something the consumer app needs to do.

Are you using the latest sign_in_with_apple: ^6.1.0 in your pubspec.yaml?

[MuhammadWaqar340]

@tp No its 3.3.0. I think sign_in_with_apple has no directly used. But some other package are dependend. I cannot find sign_in_with_apple in my pubspec.yaml file but present in pubspec.lock file. I try the solution by deleting the pubspec.lock file and regenerate it by "flutter pub get" but sign_in_with_apple automatically added to my pubspec.lock file with version 3.3.0.

[tp]

If you're not sure how this plug-in even ended up in your project, run flutter pub deps to see which package pulled it in as a dependency (via https://stackoverflow.com/questions/57174506/dependency-diagram-in-dart-flutter).

Then upgrade that one, which should hopefully refer to a more recent version of our plugin here.

There is no other way than upgrading the plugin to get this fixed for you (or drop the dependency, if you don't even want to use sign_in_with_apple). (If you're not using it in practice but have a dependency that is pulling it in, you might also be able to use dependency_overrides to force a later version.)

[MuhammadWaqar340]

@tp Thanks for your time. I resolved the issue by dependency_overrides and its work for me.