Geek Answers Handbook

ERROR: dump failed because AndroidManifest.xml was not found

When I try to download the application to the android game store, I get the following error:

ERROR: dump failed because no AndroidManifest.xml found

The steps I took:

  • new hard drive, install clean jre, jdk
  • download Android eclipse package - latest version today
  • create a new project, sample. simple world greetings
  • sign it using the wizard, create a certificate, etc.
  • try uploading it to the market ... = ERROR!

I tried many combinations, different versions of the eclipse. even sign it manually. It does not work if I try to run the dump assembler, I get the same error.

if anyone knows a solution ...

(LATER EDIT): The quickest solution you can find without having to bang your head against a wall is in my own accepted answer below. Anyway, InteliJ is 100 times superior to Eclipse.

+8
android eclipse google-play
source share
4 answers

decision:

  • compile it and export the project under linux (eclipse)
  • upgrade to InteliJ Studio ( recommended )

It seems that from time to time there is a problem with the eclipse under windows 7.8

+1
source share

The following items must be taken care of when uploading a file to the android market

"android: versionCode" of AndroidManifest.xml is correct. The attribute "android: versionName" from AndroidManifest.xml is correct. The name of the package is very unique. Because all applications on the Android market are separated by a package.

see it all in place ....

taken from when downloading a file to an Android market error

+3
source share

OPTION # 1: Slow down re-read each step. ( Source ).

The main setting for the signature.

Before you begin, make sure that the Keytool utility and the Jarsigner utility are available for 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 the JAVA_HOME environment so it references the appropriate JDK. Alternatively, you can add the JDK version of Keytool and Jarsigner for your PATH variable.

...

Eclipse Users

If you are running Eclipse / ADT (and configured Keytool and Jarsigner as described above in Basic Setup for Signing), logging in debugging mode is enabled by default. When you launch or debug your application, ADT signs a .apk file with a debug certificate, runs zipalign on the package, then installs it on the selected emulator or connected device. No specific action is required on your part, ADT has access to Keytool.

OPTION # 2: Check the features required by your application with unsigned “.apk”. ( 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 functions and permissions. To do this, start aapt using the dump icon command. This leads to an analysis of your application manifest and apply the same rules used by Google Play to determine the features that your application requires.

To use the tool, follow these steps:

First create and export the application as an unsigned .apk. if you are developing in Eclipse using the ADT, right-click the project and select Android Tools> Export Unsigned Application Package. Select the path file name and path, and click OK. Then find the tool if it is not already in your PATH. If you use SDK Tools r8 or higher, you can find the file 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.

Launch aapt using this syntax:

 $ aapt dump badging <path_to_exported_.apk>
+3
source share

An error occurred while starting xamarin.uitest when using the Android SDK 29 build tools. The problem was solved by changing the Android SDK build tools to 28.

0
source share

More articles:


All Articles