ERRORE: discarica non è riuscita perché non AndroidManifest.xml trovato

Question

Quando provo a caricare un'applicazione per Android playstore ricevo il seguente errore:

ERROR: dump failed because no AndroidManifest.xml found 

passaggi che ho preso:

• nuovo HDD, installa clean jre, jdk
• download pacchetto android eclipse - ultima versione oggi
• creare un nuovo progetto, campione. semplice ciao mondo
• firmalo con la procedura guidata, crea un certificato ecc.
• prova a caricarlo sul mercato ... = ERRORE!

Ho provato molte combinazioni, diverse versioni di eclissi. anche per firmarlo manualmente. non funziona se provo a eseguire aapt dump badging ottengo lo stesso errore.

se qualcuno sa di una soluzione ...

(PIÙ TARDI EDIT): la soluzione più veloce si possono trovare, senza dover battere la testa nel muro, è nella mia risposta accettato di seguito. comunque, InteliJ è 100 volte migliore di Eclipse.

Answer 1

soluzione:

• compilare esso & esportare il progetto sotto linux (Eclipse)
• interruttore per InteliJ Studio (raccomandato)

sembra di volta in ora c'è un problema con eclipse sotto Windows 7,8

Answer 2

following points are need to be taken care of while uploading file on android market

"android:versionCode" attribute from AndroidManifest.xml is proper. "android:versionName" attribute from AndroidManifest.xml is proper. The package name is very unique,. Because all the apps on android market are separated by the package.

see all this is in place....

tratto da while uploading file to android market error

Answer 3

OPZIONE # 1: Rallentare un rileggere ogni passo. (Source).

Basic Setup for Signing.

Before you begin, make sure that the Keytool utility and Jarsigner utility are available to the SDK build tools. Both of these tools are available in the JDK. In most cases, you can tell the SDK build tools how to find these utilities by setting your JAVA_HOME environment variable so it references a suitable JDK. Alternatively, you can add the JDK version of Keytool and Jarsigner to your PATH variable.

...

Eclipse Users

If you are developing in Eclipse/ADT (and have set up Keytool and Jarsigner as described above in Basic Setup for Signing), signing in debug mode is enabled by default. When you run or debug your application, ADT signs the .apk file with the debug certificate, runs zipalign on the package, then installs it on the selected emulator or connected device. No specific action on your part is needed, provided ADT has access to Keytool.

OPZIONE # 2: prova le caratteristiche richieste dalla vostra applicazione con un '.apk' senza segno. (Source).

You can use the aapt tool, included in the Android SDK, to determine how Google Play will filter your application, based on its declared features and permissions. To do so, run aapt with the dump badging command. This causes aapt to parse your application's manifest and apply the same rules as used by Google Play to determine the features that your application requires.

To use the tool, follow these steps:

First, build and export your application as an unsigned .apk. If you are developing in Eclipse with ADT, right-click the project and select Android Tools > Export Unsigned Application Package. Select a destination filename and path and click OK. Next, locate the aapt tool, if it is not already in your PATH. If you are using SDK Tools r8 or higher, you can find aapt in the /platform-tools/ directory. Note: You must use the version of aapt that is provided for the latest Platform-Tools component available. If you do not have the latest Platform-Tools component, download it using the Android SDK Manager.

Run aapt using this syntax:

$ aapt dump badging <path_to_exported_.apk>