Any clue as to why a signed app would fail to install vs an unsigned app? Install is happening via APK. App is built with 1.5, using Google 2.2 api's. If you need any additional info let me know..

Hi Zackamo, Would you mind giving as much detail to the problem as possible? It's kind of hard to diagnose an issue wit so little to go on.

Sure, had a feeling I was providing enough, but not clear as to where to start with details. Using the following: Windows 7 64 bit JDK 1.7.0_01 Eclipse - Indigo Service Release 1 - Build id: 20110916-0149 I have tried to tweak the manifest from debuggable to non debuggable, not sure this is necessary, but information. I am exporting the app by right click project folder -> Android Tools ->Export Signed Package. When trying to install the signed package on my phone, it confirms permissions, and then goes to install status bar. It sits there for a bit then goes to a screen with a message program not installed. My phone is a AT&T captivate running CM7. My gut tells me I must have tweaked something and not realized it, so I might try to download source and try from scratch, but any additional info would be great. If I am still missing major specifics about my project let me know...

Does you app succesfully run on the simulator? Are there any errors or warnings when trying to do so? It will probably be very helpful to spend some time here to get a good idea of the process for building and releasing: http://developer.android.com/guide/publishing/publishing_overview.html There is a sections dedicated to signing that will probably help you out.