Android studio apk signature verification failed

Apksigner does not verify signature

i was trying to verify the signature of the latest Gmail App (Version 8.11.25.224) with apksigner and it failed.

apksigner verifiy —verbose —print-certs

I was searching for an explanation why this happend but I couldn’t find any solution to this problem. I have experimented a little and if you add —min-sdk-version 28 to the options of apksigner command then the results are:

And if you use the jarsigner tool the results are:

Re-run with the -verbose and -certs options for more details. I uploaded my Gmail APK file.

2 Answers 2

This happens if an APK is signed with v3 signing scheme but the version of apksigner is outdated and not supporting this scheme. Read the warning:

So, the signature algorithm is unknown to apksigner version 0.8. I wouldn’t call it a bug (as Pierre does), but the error message could be more clear and it would be better if the old version is able to check at least the v2 signature. The most annoying point (mentioned by Freedo) is that Ubuntu still ships an old 0.8 apksigner package for all releases (packages.ubuntu.com) even the most recent Ubuntu 19.10 (eoan) and there is no ppa with a newer version. You need at least version 0.9 which is currently only part of the Android SDK build tools.

The easiest way for me was to install Android Studio and open it at least once to automatically download the latest Android SDK. Ubuntu 19.10 App Center did install it as snap and the SDK was then located in my home directory:

There are a lot of warning about files in the META-INF folder, because the folder is excluded from the signature, contains a lot of version files and the certs. That’s also the reason why it is not sufficient to just read the cert from the APK, like some some pages recommend.

Источник

Unable to generate new signed apk Password verification failed

I have generated an app bundle and published it in the play store successfully. Now I am trying to generate a signed apk(to test in device) and I am getting Password verification failed. I googled and tried every solutions found in stackoverflow, but nothing solved my problem. Then I tried generating a new keystore with new alias and passwords. Again I am getting same error for the new keystore also. I am using Android Studio 3.3, gradle 3.3.1.

9 Answers 9

I was with the same problem.
Try to clean Project and then Rebuild Project!
It Solved my problem

I ran into the same problem on upgrade to android studio 4.2.

The following steps solved the problem:

1. Update gradle plugin to the latest
2. Build -> Clean project
3. File -> Invalidate caches / restart
4. Build -> generate signed bundle / apk.
5. Delete the existing pre-typed passwords, and type them again.

Updating the gradle to latest version solved the issue. I was having gradle 3.3.0, updating it to 3.3.1 solved the issue. Thought of sharing it as it may solve the issue for someone if they are facing the same problem.

I was also stuck with same problem. i was keeping the same password as keystore password I tried with other password and it worked.

Generate an upload key and keystore If you don’t already have an upload key, which is useful when opting in to App signing by Google Play, you can generate one using Android Studio as follows:

1)In the menu bar, click Build > Build > Generate Signed Bundle/APK.

2)In the Generate Signed Bundle or APK dialog, select Android App Bundle or APK and click Next.

3)Below the field for Key store path, click Create new.

4)On the New Key Store window, provide the following information for your keystore and key,

Key store path: Select the location where your keystore should be created.

Password: Create and confirm a secure password for your keystore.

Alias: Enter an identifying name for your key.

Password: Create and confirm a secure password for your key. This should be different from the password you chose for your keystore.

Validity (years): Set the length of time in years that your key will be valid. Your key should be valid for at least 25 years, so you can sign app updates with the same key through the lifespan of your app.

Certificate: Enter some information about yourself for your certificate. This information is not displayed in your app, but is included in your certificate as part of the APK.

7)Once you complete the form, click OK.

8)If you would like to build and sign your app with your upload key, continue to the section about how to Sign your app with your upload key. If only want to generate the key and keystore, click Cancel.

Источник

Что такое INSTALL PARSE FAILED NO CERTIFICATES error?

Я пытался изменить свою активность по умолчанию/main/startup (как бы Вы ее ни называли), отредактировав . Все, что я сделал, это изменил android:name собственность. однако это полностью сломало все приложение. когда я пытаюсь установить его, он терпит неудачу и читает.

ошибка установки: INSTALL_PARSE_FAILED_NO_CERTIFICATES

когда я попытался вернуть его в прежнее состояние, он все еще давал мне ту же ошибку. Что я наделал?

15 ответов

вы отредактировали AndroidManifest.xml непосредственно в ? Если так, то это не сработает.

Каждый Android .apk должен быть подписан, если он будет установлен на телефоне, даже если вы не устанавливаете через рынок. Инструменты разработки работают вокруг этого, подписывая сертификат разработки, но .apk все-таки подписан.

одно использование этого так устройство может сказать, если .apk является допустимым обновлением для установленного приложения, поскольку, если это так, сертификаты будут одинаковыми.

поэтому, если вы внесете какие-либо изменения в свое приложение, вам нужно будет перестроить .apk поэтому он подписывается правильно.

Я обнаружил, что эта ошибка также может возникнуть при использовании неправильной конфигурации подписи. Как описано здесь, Android 7.0 представляет новую схему подписи,V2. Схема V2 подписывает весь APK, а не только банку, как это делается в схеме V1. Если вы подписываете только V2 и пытаетесь установить на целевой объект pre-7.0, вы получите эту ошибку, так как сами банки не подписаны и pre-7.0 PackageManager не удается обнаружить присутствие V2 apk подпись.

чтобы быть совместимым со всеми целевыми системами, убедитесь, что APK подписан с обеими схемами, проверив оба поля версии подписи в Android Studio создать подписанный APK диалоговое окно как показано ниже:

Если ожидаются только цели 7.0, то нет необходимости включать подпись V1.

я обнаружил, что это было вызвано моей версией JDK.

у меня была эта проблема с «ant» , и это было связано с этой осторожностью, упомянутой в документации:

внимание: начиная с JDK 7, алгоритм подписи по умолчанию изменился, требуя, чтобы вы указывали подписи и дайджест алгоритмов (- sigalg и-digestalg) при подписании АПК.

у меня есть JDK 7. В моем журнале муравьев я использовал -v для многословия, и он показал

Я подписал банку вручную и выровнял ее, но она дала немного другую ошибку:

Я нашел, что ответил Здесь.

мне нужно было только удалить его, а затем он работал!

теперь мне нужно только изменения.xml для использования этих параметров при подписании!

Ok вот он: C:\Program файлы\Java\android-sdk\tools\ant\build.в XML

Источник

What is INSTALL_PARSE_FAILED_NO_CERTIFICATES error?

I was trying to change my default/main/startup (whatever you call it) activity by editing the androidmanifest.xml file. All i did was change the android:name property. however, this completely broke the entire app. when I try to install it fails and reads.

Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES

When I tried to change it back to its previous state, it was still giving me the same error. What have I done?

37 Answers 37

I found that this error can now also occur when using the wrong signing config. As described here, Android 7.0 introduces a new signature scheme, V2. The V2 scheme signs the entire APK rather than just the JAR, as is done in the V1 scheme. If you sign with only V2, and attempt to install on a pre-7.0 target, you’ll get this error since the JARs themselves are not signed and the pre-7.0 PackageManager cannot detect the presence of the V2 APK signature.

To be compatible with all target systems, make sure the APK is signed with both schemes by checking both signature version boxes in Android Studio’s Generate Signed APK dialog as shown here:

If only 7.0 targets are anticipated, then there is no need to include the V1 signature.

Источник

How To Fix – “INSTALL_PARSE_FAILED_NO_CERTIFICATES” Error in Android Studio ?

How To Fix – “INSTALL_PARSE_FAILED_NO_CERTIFICATES” Error in Android Studio ?

In this post , we will see How To Fix – “INSTALL_PARSE_FAILED_NO_CERTIFICATES” Error in Android Studio. You see the below error in your Android Studio

After developing an Android App , the obvious next step is to publish it for public use.

However to publish the App on Playstore , you do need to sign the app in Android Studio. Hence it is a mandatory step.

Option 1 – First Time User:

If you are using installing and setting up your Android Studio for the “First time”, you might have created a demo app in the process flow. Sometimes initially when you are setting up the Android Studio environment for the first time, things get a bit messed up while running the demo app in emulator . This leads to logging the error – “INSTALL_PARSE_FAILED_NO_CERTIFICATES”.

So try the below steps to fix –

• Click File –> Open –> Note the Folder Location. This folder holds the project files of the demo app that you have created.
• Close the Android Studio
• Go to the Folder Location and delete the project folder and all the files therein (Here I am assuming it is just a first initial demo app project – not something immensely IMPORTANT or crucial)
• Open the Android Studio now —> Start New Project —-> Create demo app again
• Run the app through the android emulator again. Hopefully this time the error should vanish by now.

Option 2 – Build using “Make Project”:

Build —-> Make Project

The “Make Project” option is one of the build-variant . It Makes all the modules as part of the Build option to compile.

Option 3 – Signature Configuration:

The Signature configuration can also cause this issue especially if you are still using an older version of Android.

The older signature scheme V1 signs just the JAR.

The later signature scheme V2 signs the entire APK.

For Older version of Android Studio , to solve this issue , get the APK signed with both of these schemes by checking both signature version boxes in Android Studio’s Generate Signed APK dialog .

For Latest Versions of Android Studio , to Solve this issue , use the below steps –

I am assuming that you don’t already have an upload key. So Let’s generate one key using Android Studio as follows:

• Go Menu —> Build —-> Generate Signed Bundle/APK.
• A Dialog will popup. Select Android App Bundle or APK —-> click Next.
• In the new popup, below the field for Key store path , click Create new.
• A new window will popup. In this New Key Store window, provide the information for keystore and key
  • Key store path: Location where keystore should be created.
  • Password: Password for keystore.
  • Alias: Use some name for your key.
  • Password: Use some secure password for your key – Different from the keystore password.
  • Validity (years): key validity in years. Key should be valid for at least 25 years . This would help you to sign app updates with the same key for many years.
  • Certificate: Use info about yourself . This information will not be displayed in the app, but will be included in the certificate as part of the APK.
• All done – click OK.

If you already have the key , export an existing app signing key, follow these steps:

• Go to Build > Generate Signed Bundle/APK.
• Select either Android App Bundle or APK and click Next.
• Select Module from the drop down.
• Use the path to your keystore, the alias for your key and passwords.
• Click Next.
• Next window , Give Destination folder name for signed app.
• Choose build type.
• Click Finish.

Источник