APK installs but won’t open after editing manifest — only v3 signature applied, v1 & v2 false

Discuss
,
1

Hey Everyone,

I’m working on a Kodular project and needed to make some changes in the AndroidManifest.xml, so I decompiled the APK, edited the manifest, then recompiled and signed it using apksigner.

The APK installs fine on my phone now, but it doesn’t actually run — the app just crashes or doesn’t open.

I ran apksigner verify to check the signature, and this is what I got:

Verified using v1 scheme (JAR signing): false
Verified using v2 scheme (APK Signature Scheme v2): false
Verified using v3 scheme (APK Signature Scheme v3): true
Verified using v3.1 scheme (APK Signature Scheme v3.1): false
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false

So only the v3 signature is valid, and I’ve read that for compatibility (especially with older Android versions), v1 and v2 signatures are also needed.

Could someone please guide me on how to sign the APK properly so that v1, v2, and v3 are all true? I’m using the apksigner.bat tool from Android Build Tools (tried both 35.0.0 and 36.0.0 versions).

Any help would really mean a lot.

2

@shrutika_kanade apksigner tool does not sign all schemes by default unless you have to

apksigner sign myy suggetion
–ks your-release-key here.jks
–ks-key-alias your-key-alias
–ks-pass pass:if you haveKeystorePassword
if needed–key-pass pass:yourKeyPassword
–v1-signing-enabled true
–v2-signing-enabled true
–v3-signing-enabled true
your-appName.apk

Note If your AndroidManifest.xml edits broke anything (like malformed XML or missing activities), even a correctly signed APK will crash.