On Wed, May 6, 2009 at 9:58 AM, guruk <[email protected]> wrote: > > thanks, but i targeted already in eclipse to 1.1 (api 2) why you say > level one ? api 3 is 1.5 and google apis as i see.
He said "-t 1" which means "target platform number 1". In the SDK the first platform is API 2. Yeah a bit confusing, I agree. > now i was able to install my old app,, deinstalled from the app > manager and now i can > compile again from eclipse and it runs on my 1.1 g1 > > now.. tripple Check: > > delete /bin/app.apk > > 1. run app in eclipse, copy /bin/app.apk to my g1 1.1 .... WORK > (file: 97.520 bytes) > delete app.apk from g1 > 2. export app.apk unsigned, install on g1 1.1 ... NOT POSSIBLE TO > INSTALL (file: 94.388 bytes (why smaller???) > 3. export app.apk signed, install on g1 1.1 .... WORK (file: 97.629 > bytes) The install process cannot change the signing key of an app. If you push an apk with a debug key (which is what happens when you run from eclipse), you cannot install a signed apk directly. You need to uninstall the debug version first. Works the other way too: if you install a signed apk, you cannot install a debug version from eclipse. You cannot push a non-signed apk at all iirc. It has to be signed either by the eclipse/ant debug key or by you manually. HTH R/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
