Android failed to export application

Question

I have a problem trying to sign my application in release mode from two to three days. I tried everything that I found as information on internet / stackoverflow and nothing worked for me. I upgrade the whole version of the SDK , update proguard to 4.7, checked jar files and conflict packages, but cannot find any solution. I included the library in my main project, but “so far I have not had any problems signing my application.

Any ideas what else I can try so that I can solve this problem, because I still read some information over the Internet and still cannot find any solution.

PS I had no problems building the debug version and running it on the device. The only problem I get is only when I try to sign my application in release mode and I get a Failed to export application error.

Answer 1

For me, Jmart's answer was good. You can easily have a rotten file name in your project.

Regardless, I am posting the answer because, like Android-Droid, I am stuck in the general message “Failed to export the application”.

But trying to export my application without a signature (see screenshot below), this time it gives me an explanation of the error! While he does not say anything when you sign using the wizard.

Hope this helps others like me!

Answer 2

Believe it or not ... I had the same problem ("android could not export .." without any other messages / messages). After many hours, I discovered a problem: I had a .jpg resource under the “Resources” folder with some special characters (ilíaco.jpg). Just remove the “offensive” nature and problem.

Answer 3

You have some errors, I would say. Try running the application in a virtual machine to see if it works. if it works, try to clean and rebuild the project and then export .. worked for me

Answer 4

Did you create your own certificate to sign the release application? Do not use the debug certificate automatically generated by Eclipse, because later you will not be able to sign the application for updating (especially if you export the project to another computer).

If so, is your certificate expiring? Do you provide good passwords?

Answer 5

http://simply-developing.blogspot.in/2013/08/eclipse-failing-during-android-export.html

try this, I looked through all these questions, and only the above link solved my problem, I could not export the dialog without errors

Answer 6

What I did was unsigned export, first, and then export. He worked, never knew what caused him.

Answer 7

For me, "Clear", and then run "Export" again - I decided it

Answer 8

I heard about using @ + id in an attribute like layout_below, layout_above, etc. can cause this problem, check this out. use this only in android cases: id = "@ + id / idid".

Answer 9

Make sure you have enough space on your OS’s hard drive!

I have a small SSD for my Windows drive, and I use other drives for my applications / data. Which had a lot of space, my SSD only had a few MB (not done for a while).

It turns out that Eclipse recorded temporary files in AppData / Local and did not have enough space to store them, causing a ridiculous general error "The application could not be exported"

Answer 10

I had some boostrap plugins containing .swf files. They have never been used or requested. Only after I deleted them did it work.

Be sure: only store images + css, html, js files, and it will never give a strange error

Answer 11

I had the same problem. This was fixed by running the application in the emulator once - finding an error (in my case, she was looking for an additional resource folder)

Bug fixed, successfully launched in the emulator - then the APK file was exported.

Hope this helps.