Your app needs to be digitally signed. If you use Eclipse with the ADT plugin, skip to the Compiling and signing with Eclipse ADT section. Otherwise, follow the instructions to export an unsigned .apk and then sign it with jarsigner.
-- Jack Ha Open Source Development Center ·T· · ·Mobile· stick together The coverage you need at the price you want The views, opinions and statements in this email are those of the author solely in their individual capacity, and do not necessarily represent those of T-Mobile USA, Inc. On Sep 12, 3:40 pm, Ken H <[email protected]> wrote: > Ok, stupid question time: what's the difference being "Export Signed > Application Package" and "Export Unsigned Application Package"? Under > 'Signing for Public Release' in the dev guide it says you must: > > 1. Compile the application in release mode > 2. Obtain a suitable private key > 3. *Sign* the application with your private key > > But then it continues: > > "To prepare your application for release...To export an unsigned .apk > from Eclipse, right-click the project in the Package Explorer and > select Android Tools > Export Unsigned Application Package." > > But below this under "Compiling and signing with Eclipse ADT" it says > to "To create a signed .apk, right-click the project in the Package > Explorer and select Android Tools > Export Signed Application > Package...When you complete the Export Wizard, you'll have a > signed .apk that's ready for distribution" > > Huh? Do I need my app signed or unsigned for distribution on market > place? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
