Bug 44540 - Cannot import APK signing identity in latest version of Xamarin for Visual Studio
Summary: Cannot import APK signing identity in latest version of Xamarin for Visual St...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-09-20 19:12 UTC by interactivegames
Modified: 2016-09-21 17:18 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description interactivegames 2016-09-20 19:12:25 UTC
With the latest version of Xamarin for Visual Studio, I cannot successfully import my signing identity when distributing an Android app. When I input the keystore password, alias, and key password, there's an error message that says the Keystore was tampered with or password was incorrect.

I was able to sign the APK using the Android commandline tools, but the same credentials I used on the commandline didn't work with Xamarin's keystore import dialog.
Comment 1 Jose Gallardo 2016-09-21 13:34:42 UTC
First of all thank for reporting.
We already had a similar report which ended up being the user entering the values in the same order the old dialog has without corresponding to what the new dialog is actually asking for.
Can you please double check if that's not the case? We might need to evaluate if reordering the fields is a good ux improvement for a more straightforward feature adoption.

If that's not the case, can you please attach the logs after a failed keystore import? From the VS menu Help - Xamarin - Zip logs

Thanks again!
Comment 2 interactivegames 2016-09-21 15:01:02 UTC
I changed the order of passwords that I entered, and I was able to import the key successfully.

The Android Studio key import dialog asks for the following values in this order:

Keystore file
Keystore password
Key alias
Key password

The fields I saw in the corresponding Xamarin dialog were:

Key Password

This confused me because Key Password means something different in Xamarin compared to Android Studio.
Comment 3 Jose Gallardo 2016-09-21 17:18:31 UTC
Thanks for letting us know.
Marking the bug as Resolved - Answered.