Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
When Publishing an Android app from Visual Studio and it fails trying to sign the package, the logs and output state the following
There was an error attempting to sign pakage: jarsigner: key associated with [aliasofkeystore] not a private key
Sample app can be provided on request
This typo should be fixed now (cycle 8). In fact, we're using a totally different publishing approach based on the Archive Manager. It's already on the Alpha Channel.
Please give it a try if you have the chance.
Thanks for reporting!
I am also able to reproduce this Issue with stable XVS (22.214.171.124). Using the wrong password I am getting same error in output: "Xamarin.VisualStudio.ProgressReport Error: 0 : [2016-08-04 16:34:31.8702] System.Exception: There was an error attempting to sign pakage: jarsigner: key associated with 360logica not a private key"
I also checked the same with Cycle 8 build (126.96.36.1999), here publishing functionality has totally changed. But if I am using wrong password or alias then I am getting following error "(Inner Exception #0) Xamarin.AndroidTools.AndroidSdkToolException: keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect"
Environment Info: https://gist.github.com/danish360/5f6b908189e8aac8621902caaac82803
Please let me know if this is correct error message now.
As per comment#3, publishing workflow has changed and I am not seeing this issue with latest Cycle 8 build (188.8.131.529).