Xamarin visual studio 2015 sha1 signature

Question

1.00/5 (2 votes)

See more:

Hi, i just changed my question to add more step. hope this help to understand my problem.

The APK was originally created using Xamarin Studio for windows (back in early 2016).
I then take over and now using Visual studio to create an APK package.

The keystore has not been provided to me, so i had to extract from the current APK package the .Keystore file from the .rsa file contained into the APK using keytool from java.
once this done i have been able to get the alias and i have also been provided the .keystore password.

I have the "archive" in visual studio in release build my code, using ad hoc publishing i have imported the .keystore file and published with the correct alias and password, but the resulting sha are not the same.

is there somethign i have done not correctly or is it that VS does not used properly the .keystore imported.

is there a way, using command line tool to "resign" and APK from a .keystore file

Thank's

What I have tried:

create a package from visual studio

Posted 28-Jan-17 1:26am

Member 12971575

Updated 30-Jan-17 4:37am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2017-01-28T01:46:00

The only way to get an identical SHA-1 signature is to have identical contents: that's the whole idea of using an SHA-1 hash value. If they are different, then the content is different, and probably not valid - that is the whole idea.
If you have a different hash, then it may be as simple as the original including a build time, date, or version code in the APK - any change, no matter how trivial will generate a different SHA-1 value.