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. ADB version error

I'm having the same error message regarding the adb, only I downloaded
the m5-rc15 windows version of the SDK.   Did this happen to me as
well?  And if so, what should I download (the newest version appears
to be what I have)?



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

2. Escaping values in SQL Queries

Hi all

When using the SQLite functions in the Android API is there a way to
escape special character in a string before using it in a query?

I am a little worried about forming queries using code such as
"... FIELD=\"" + value + "\" ... "
in case the value contains special characters. Not escaping values
properly can result in SQL Injection Vulnerabilities is data is from
untrusted sources, and we certainly would not want that!

Does the whereArgs in the update method call get escaped automatically?
Does this apply to Strings passed to ConentValues as well?

Thanks

Andy

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

3. Where should I report this?

4. How many meters can fit the screen example

5. Currently supported video formats + max. video file sizes for Android?

6. Phone call

7. Linkify Text -- Focus disappears while navigating between more than one?