Installation unsuccessful - Package file was not signed correctly

by joshv » Mon, 15 Dec 2008 14:46:05 GMT


Sponsored Links
 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?

--~--~---------~--~----~------------~-------~--~----~



Installation unsuccessful - Package file was not signed correctly

by joshv » Mon, 15 Dec 2008 15:48:01 GMT


 Solved my own problem by watching logcat during the installation:

12-15 01:28:27.722: ERROR/PackageParser(56): Package
com.quirkconsulting.ticker has no certificates at entry res/anim/
push_down_in.xml; ignoring!

I removed this particular file, re-exported/signed the apk, and it
worked perfectly.  jarsigner -verify reported this file as signed, but
something about it killed the PackageParser.

Could this be related to this bug?

 http://code.google.com/p/android/issues/detail?id=830 

-josh



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Installation unsuccessful - Package file was not signed correctly

by Mark K » Tue, 16 Dec 2008 03:25:06 GMT


 Is your self generated certificate valid until 2033? If you use the
default, it will only have a validity of 180 days, use -validity 10000
when generating your cert. Just something to check. Maybe try
generating a new cert.

                         M



--~--~---------~--~----~------------~-------~--~----~



Installation unsuccessful - Package file was not signed correctly

by joshv » Tue, 16 Dec 2008 04:23:59 GMT


 I followed the instructions properly when creating the cert, and it's
valid until 2033.

As I mentioned, I only had to remove the offending file, re-sign the
apk, and everything worked just fine, with the exact same certificate,
so the cert hasn't expired.

There's either something wrong with the export/packager, or something
wrong with the PackageParser.  I just hope I don't bump into this
again, as it appears to be quite random - there was nothing special
about the animation file that the PackageParser died on.




--~--~---------~--~----~------------~-------~--~----~



Installation unsuccessful - Package file was not signed correctly

by Craig » Mon, 06 Apr 2009 17:45:42 GMT


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



Installation unsuccessful - Package file was not signed correctly

by myth2loki » Wed, 29 Apr 2009 01:07:38 GMT


 I met the same problem,how to fix it?it will drive me crazy
soon.Help....




--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Is it possible for my Activity to be notified when the external storage state changes?

I would like my Activity to be informed when the SD card is removed,
since it relies on files from the SD card (to keep apk size down) but
for compatibility reasons is not targeted at Froyo.

I'd like to close the application when the SD card is removed/mounted
(giving the user a dialog message to inform them of course) so that I
don't get IOExceptions etc (I'd quite like to not have to check
everytime I load a file to see if the external storage is available, I
already do a check on application launch).

There doesn't seem to be any attribute in the manifest for this (like
configChanges) that I can find.

-- 

2. Andriod Email Flaw

Hello I have noticed a flaw in Android,  When connecting to an IMAP
server Doesn't matter if it is Exhange or Unix the Android Email
client will not close the connection.  In order for IMAP to work
correctly a client makes a conneciton and gets updates. If a
connection to the IMAP server is left opened you will not see any new
updates.

Step by step on how it should work.

Example will be Exchange server:

Create a new connection point to your IMAP server (Exchange) port 143
(cleartext) or 993 (Secure)
add username: John Doe
Add Domain: *Optional with VPN
Password: **************
SMTP server (Exchange)

How often to login and check 5 10 15 30 1hr
Logout after checking email YES/NO (Ding ding ding grand prize winner
option here)

This is a simple fix for Google engineers to fix, they should include
it in their next rev.

-- 

3. ImageView setColorFilter, what to do for a bitmap?

4. Vector Graphics Rendering - Mechanisms

5. Recent Apps change in 2.2 - Brings main Activity to foreground, not the last visible one

6. SQLiteOpenHelper per activity??

7. How to override the <ENTER> key behaviour of the virtual keyboard in Android