I am signing my apk using the below command:
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore mykeystore.keystore myApp.apk aliasname
The log ends with
.
.
.
signing: org/achartengine/image/zoom-1.png
signing: org/achartengine/image/zoom_in.png
signing: org/achartengine/image/zoom_out.png
signing: LICENSE.txt
signing: assets/cpwrUEM-instr-runtime.properties
jar signed.
But when I run the verification command:
jarsigner -verify -verbose -certs myApp.apk
I get the below error:
jarsigner: java.lang.SecurityException: invalid SHA1 signature file digest for res/drawable-hdpi-v4/btn_large.png
Most of the forums mentions that when we get the above error message we should resign the jar by adding -digestalg SHA1. But I already have that and still get the same exception.
On trying to install on a device, I get the message
There is a problem parsing the package.
UPDATE:
On changing the algorithm from SHA1 to SHA-256 it stills give me the same exception but this time on a xml file.
Verify if the apk you are signing is originally unsigned or not. If not, export the unsigned version using the Android Tools in your IDE.
Related
I'm using ionic for developing an android app. I jarsigned my app by mistake with an new keystore. As I got the error that the certifikate is unequal by uploading the app to the play store I used my backup keystore file with the same certificate needed in playstore.
Now if I want to jarsign my .apk with the command
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore app-release-unsigned.apk MyApp.apk alias_name
I get the following error
jarsigner error: java.lang.RuntimeException: keystore load: Invalid keystore format
I googled a lot but I am not sure if any of the solutions could help me. I have to use my old certificate and cannot use a new one because I can't upload it then to playstore.
What do I have to do that it works again?
Just like the error says, you have an issue with the format of your keystore. Check the -keystore argument in your jarsigner command line op. It's an .apk file when it should be your .keystore file.
Do like this:
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore HelloWorld-release-unsigned.apk alias_name
I used the Dynatrace auto-instrumentor command on my Android apk file
auto-instrumentor.cmd apk <apk file> prop <APK-Instr.properties>
and then signed it with my keystore.
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore mykeystore.keystore myApp.apk aliasname
Finally I zip align it using the below command:
zipalign -f -v 4 AppFile.apk AppFile2.apk
But when I try to install the file, I get a parsing error:
There is a problem parsing the package.
Note: I have been able to successfully verify the jar using the below command:
jarsigner -verify -keystore mystore.keystore AppFile.apk
But still get the parsing error!
Try using changing the hash algorithms and retrying. You may use either SHA2 or SHA256 as a start.
Note that SHA1 is being deprecated by browsers.
It's possible that your APK was signed with a debug key when it was first built. Running jarsigner again could be signing it a second time.
Take a look at this question and my answer here to see if this is the problem.
I have created an APK using Unity but cannot upload it onto GooglePlay because it isn't assigned. I saw many pages on how can I solve it using Unity, but I am using a Mac.
I tried changing .apk to .zip and then changing the parameters in .xml (manifest) accordingly, but GooglePlay shows:
You uploaded an APK that is not zip aligned. You will need to run a
zip align tool on your APK and upload it again.
Please help.
With command-lines, you can sign(with jarsigner from the java-jdk) and align(with zipalign from the android-SDK).
Sign:jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore my-release-key.keystore my_application.apk alias_name
Align:zipalign -v 4 your_project_name-unaligned.apk your_project_name.apk
Having the error: unable to sign jar: java.util.zip.ZipException: invalid entry compressed size ... means that the apk is already signed, you should:
Verify that it's not signed with the debug-key:jarsigner -verify -verbose -certs my_application.apk.
Remove the debug-signature if needed:zip -d foo.apk META-INF/\*
When I verify the signature of my application:
jarsigner -verify -verbose -certs testapp.apk
it gives me the error:
jarsigner: java.lang.SecurityException: invalid SHA1 signature file digest for res/drawable-xhdpi/breadcrumb_grey_white.png
How to resolve this?
make sure to delete the META_INF folder in the apk before signing it.
Also, if you are using JDK 7, then include the the option -sigalg MD5withRSA when signing with the jarsigner along with -digestalg SHA1 mentioned by Andrejs
Ripped from here.
Here is the solution:
jarsigner -keystore mykeystore -digestalg SHA1 jarfile alias
To verify:
jarsigner -verify -verbose -certs jarfile
I've been trying to use the jarsigner.exe and adb.exe to manually sign an android package and install it on a API V8 emulator. I created a simple HelloAndroid project and it would generate a signed HelloAndroid.apk using the debug.keystore located in the user's .android directory. When launching from Eclipse, it builds and installs the apk on the emulator without a problem.
I used the android tools to export an unsigned application package to a separate directory. I signed and zipAligned the package and used adb to install it but received the error:
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
I used the following command to sign it.
jarsigner -verbose -keystore c:\users\jhwong\.android\debug.keystore
-storepass android -keypass android -digestalg SHA-1 -sigalg SHA1withRSA
-sigfile CERT -signedjar temp\HelloWorld2.apk
temp\HelloWorld.unsigned.apk androiddebugkey
adding: META-INF/MANIFEST.MF
adding: META-INF/CERT.SF
adding: META-INF/CERT.RSA
signing: res/layout/main.xml
signing: AndroidManifest.xml
signing: resources.arsc
signing: res/drawable-hdpi/icon.png
signing: res/drawable-ldpi/icon.png
signing: res/drawable-mdpi/icon.png
signing: classes.dex
That did not give me any errors and just to makes sure I ran:
jarsigner -verify -verbose temp\HelloWorld2.apk
It showed the jar was verified and each file signed and part of the manifest.
I ran zipalign -v 4 temp\HelloWorld2.apk temp\HelloWorld3.apk which finished without an error.
Then used adb install -r temp\HelloWorld3.apk.
I've seen several related threads and articles suggesting these directions but I'm perplexed as to why it doesn't work manually verses using Eclipse to build the signed package. I've even taken the package built from Eclipse and was able to use adb.exe to install it so I've narrowed it to signing the package. I've tried keystores that I've generated from the keytool but they didn't work as well which is why I tried the debug.keystore.
I'd appreciate any advice if they noticed anything wrong with my jarsigner code.
We had this exact same problem. Try using the following parameter values:
jarsigner ... -digestalg SHA1 -sigalg MD5withRSA ...
By the way, using explicit sigalg and digestalg seems to be mandatory with JDK 7.
To sign apks using JDK 1.7 one has to use these keywords "-sigalg MD5withRSA -digestalg SHA1 "
Reason:
As of JDK 7, the default signing algorithim has changed, requiring you to specify the signature and digest algorithims (-sigalg and -digestalg) when you sign an APK.
Command:
jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore [keystorefile]
[originalapk] alias_name
If you're using JDK 7, try
jarsigner -sigalg SHA1withRSA -digestalg SHA1
If you get
jarsigner error: java.security.SignatureException: private key algorithm is not compatible with signature algorithm
then try
jarsigner -sigalg MD5withRSA -digestalg SHA1