[android-developers] Installation unsuccessful - Package file was not signed correctly

2009-04-06 Thread Craig

I published my app on the market, and when I first tried installing it
from there, I got the 'package file was not signed correctly' error.
Uninstalling the unsigned version I was testing with let me install
from the market with no problems. However, from the comments, it looks
like no one else can install my application.

I've put other versions up that worked, and I used the same
certificate, so I'm pretty sure it is not an issue with the validity
days for the certificate.

Any idea what I can do to figure this out?

The name of my application is Bloxors. It will be going up and down as
I try to figure out what the issue is here, but if someone else who is
getting the error can debug it it would be greatly appreciated.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



[android-developers] Installation unsuccessful - Package file was not signed correctly

2008-12-14 Thread joshv

I am becoming somewhat terrified of uploading upgrades to my market
apps, because it always seems to break something.

This time around, I followed the exact same process as I always do,
export the unsigned jar, sign it, verify that its signed with
jarsigner -verify and then upload it as an upgrade to the market.

When I attempt to install the app from the market I get Installation
unsuccessful, with the reason Package file was not signed
correctly.  Which is somewhat amazing to me, because the upload page
won't let you upload an unsigned jar.

Am I missing something here?  I used the exact same command line to
sign the jar that I've used for the past updates that worked:

jarsigner -verbose -keystore c:\path_to_keystore application.apk quirk

And no, I have NOT changed my certificate, it's been the same since I
created it, and has been used for many previous updates.

Basically at this point I had to remove my app from the market as
nobody can install it.

Any ideas on how to trouble shoot?

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---