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
On Dec 14, 10:46 pm, joshv <[email protected]> wrote:
> 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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
