0

You uploaded an APK with an invalid signature (learn more about signing). Error from apksigner: ERROR: MIN_SIG_SCHEME_FOR_TARGET_SDK_NOT_MET: Target SDK version 30 requires a minimum of signature scheme v2; the APK is not signed with this or a later signature scheme

Pankaj
  • 1

2 Answers2

0

You need to update version min 30

  compileSdkVersion 30
buildToolsVersion "30.0.3"

defaultConfig {
    applicationId "com.xxx.xxxxd"
    minSdkVersion 21
    targetSdkVersion 30
    versionCode 1
    versionName "1.0"

    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}
mehul chauhan
  • 1,792
  • 11
  • 26
0

when signing apk it will show you signature versions below remember to check V2 Full APK Signature or start using AAB

check V2 Full signature down below

V2 Signing is minimum Signature Scheme as of now and V3 is also on the line for more details refer this link and to know more about app signing refer this link.

trinadh thatakula
  • 807
  • 5
  • 18
  • Sir,V1 and v2 signature are disable and not tickable in my case. – Pankaj Jul 07 '21 at 08:17
  • which version of android studio and android gradle plugin are you using ? also try updating gradle plugin to latest stable 4.2.2 – trinadh thatakula Jul 07 '21 at 09:15
  • same issue was already faced by others you can find more details at https://stackoverflow.com/q/43525209/8968956 – trinadh thatakula Jul 07 '21 at 09:17
  • 3.3.2 android studio – Pankaj Jul 07 '21 at 09:46
  • after change the gradle version – Pankaj Jul 07 '21 at 10:16
  • org.gradle.api.internal.tasks.DefaultTaskInputs$TaskInputUnionFileCollection cannot be cast to org.gradle.api.internal.file.collections.DefaultConfigurableFileCollection Possible causes for this unexpected error include: Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.) Re-download dependencies and sync project (requires network) – Pankaj Jul 07 '21 at 10:17
  • The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem. Stop Gradle build processes (requires restart) Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project. In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes. – Pankaj Jul 07 '21 at 10:17
  • i think issue here is related to your android studio and gradle plugin so try reinstalling newer version of android studio and try again latest stable version is 4.2.2 – trinadh thatakula Jul 08 '21 at 11:04