Had a request from someone to elaborate on what I did to fix this.
This issue started showing up when I started building with the 1.6
SDK.

When I signed the application with a new certificate, the problem went
away.  Here's what I did:

1. created a new certificate using the instructions on this web page:
http://developer.android.com/guide/publishing/app-signing.html
2. Exported the signed package using Eclipse: Right Click Project ->
Export Signed Application Package -> follow dialog boxes.

Also, make sure the phone is upgraded.

If you're still having issues after doing this, then either my fix
isn't the right one, or there's another problem.

Hope that helps.

Richard


On Oct 12, 11:38 am, Richard Schilling
<richard.rootwirel...@gmail.com> wrote:
> Oh, the android should be upgrading the old application properly, so
> uninstalling should not be necessary.  This is an upgrade.
>
> Richard
>
> On Oct 12, 11:37 am, Richard Schilling
>
> <richard.rootwirel...@gmail.com> wrote:
> > The issue seems to be with the certificate used to sign the
> > application.  It works now.
>
> > What I would like to do is submit a patch that provides more verbose
> > information about why an install fails (e.g. certificate is invalid).
>
> > Looking into PackageInstaller to see what I can find.
>
> > Richard
>
> > On Oct 12, 10:57 am, "nEx.Software" <email.nex.softw...@gmail.com>
> > wrote:
>
> > > Obvious question alert: Did you remove any old version you might have
> > > had hadinstalledbefore trying to install the new one?
>
> > > On Oct 12, 10:28 am, Richard Schilling
>
> > > <richard.rootwirel...@gmail.com> wrote:
> > > > I am seeing this now too.  Just upgraded thephoneto 1.6.  DDMS
> > > > doesn't tell me squat.
>
> > > > Anyone?
>
> > > > Richard Schilling
> > > > Mobile Operating System Engineer
> > > > Root Wireless, Inc.
>
> > > > On Aug 14, 8:32 pm, dougx <douglas.lin...@gmail.com> wrote:
>
> > > > > I just rebuilt an application to use some new assets, and now I get
> > > > > this message on myphonewhen I try to install it:
>
> > > > > "Applicationnotinstalled"
> > > > > "UnitTestscouldnotbeinstalledon thisphone"
>
> > > > > Anyone know what's going on?
>
> > > > > I've checked and I've definitely got "Unknown sources" ticked on the
> > > > > application settings.
>
> > > > > This is just a self signed application to run my unit tests on an
> > > > > actualphone(the emulator doesn't cut it for real testing). I tried
> > > > > creating a new keystore, and they didn't help.
>
> > > > > What on earth?
>
> > > > > The only thing I can think of that I've done recently is accept a
> > > > > google security update... >_<
> > > > > If they've silently done some other updates that prevent self signed
> > > > > applications running, I'm severely upset.
>
> > > > > Anyone seen this?
>
> > > > > ~
> > > > > Doug.
--~--~---------~--~----~------------~-------~--~----~
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