On Jul 28, 2011, at 6:28 PM, John Murray wrote: > I believe I’ve got all my parameters right but mono develop simply reports > ‘failed to sign package’ > Any idea where I look nect to find out what I am doing wrong ?
Best we can suggest is enabling Verbose output, via MonoDevelop > Preferences, (Preferences / Build) in the tree, General tab, Log verbosity drop-down on the right. > In the \bin\release folder there is a built version of the package named > Agar14-signed.apk > This is timed at a time when I was using Vis Studio – so next question does > vis studio automatically create signed packages? All packages are automatically signed -- they need to be or they can't be deployed anywhere for debugging. :-) Thus the real question is this: what is used to sign the package? By default a temporary certificate is created for each project to sign the .apk for debugging. You can specify your own certificate/keystore by following: http://android.xamarin.com/Documentation/Guides/Preparing_Package_for_Android_Marketplace#Step_4_-_Sign_the_Package http://android.xamarin.com/Documentation/Build_Process#Signing If you're able to deploy a debug package to the device (which presumably you're able to), then keytool/jarsigner/etc. can be found and are working, so the problem is likely that incorrect arguments are being passed to the tools. Hopefully increasing the build verbosity will help narrow down the problem. - Jon _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
