Although I am using the same certificate and keystore, I am not able
to upload an upgrade of my application to the Android Market.  The key
is the same but may not appear to be since I changed platforms from PC
to Mac.  It is also possible that this is my mistake rather than a
bug.  Although the keystore is obviously named and the password is
correct, I might have created and used some other key...  It has been
months since I uploaded the last version of the app.  Is there
anything I can do to override the certificate errors I am hitting when
I use the 'upload upgrade' link?

The error is "The apk must be signed with at least one certificate in
common with the previous version."
To try and get around this, I unpublished, put in the updated apk, got
the same error, still no go. I unpublished and pushed out a refactored
apk.  No go.
I finally refactored to change the package name which allows me to
upload the upgrade as a new application. Of course, the old app is
still in place and I can't migrate existing users to give them the
upgrade.  Can I solve this problem?  If not, the Market is going to be
a mess of many versions of the same applications. (it already is
messed up this way, no? :)

Of course I like the added security of encryption and certificates so
that nobody can hack my app and upload malicious code under my name.
Today the protection is hampering my efforts, today it is inflexible.
Can I get a one time work-around for the certificate requirement so
that an upgrade will be published without the same certificate?  Any
feedback will be appreciated.

Regards,
Beth

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to