i'm not using my own key stuffs... didn't know that was an option. using monodevelop btw.
source for this project is available at <<https://gitorious.org/ampache-net >> On Tue, Dec 6, 2011 at 3:39 AM, Jonathan Pobst <[email protected]> wrote: > If you were using your own key stuffs in the csproj, like this: > > http://docs.xamarin.com/android/tutorials/Preparing_Package_for_Android_Marketplace#Permanently_Use_A_Different_Keystore > > Then we fixed a bug where the KeyPass and StorePass were backwards. Try > switching the 2 in your csproj and see if that fixes it. > > I *think* if you sign with a new key, it will be a new application on the > marketplace. You will not be able to push upgrades to your old one. > > Jonathan > > > On 12/5/2011 9:30 PM, jcwmoore wrote: > >> just updated to 4.0 (excellent btw ) and after cleaning up my app to build >> with the update toolkit i am now unable to "Publish Android Application" >> when using an existing key store, i.e. the key store i used with version >> 1.2... will there be any ill effects if a create a new key store and >> update >> my existing app on the market? >> >> always, >> http://johnclaytonmoore.com john >> >> -- >> View this message in context: >> http://mono-for-android.1047100.n5.nabble.com/unable-to-use-existing-keystore-after-4-0-update-tp5050929p5050929.html >> Sent from the Mono for Android mailing list archive at Nabble.com. >> _______________________________________________ >> Monodroid mailing list >> [email protected] >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid >> >> >> >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
