Conversion to Dalvik format failed with error 1 Solution?

Question

I was programming an application for android, after i added a tab layout to the program an error showed up to:

Conversion to Dalvik format failed with error 1

I have tried cleaning the project and looking at all the other solution to the problem on this website. Has someone also found some obscure solution to this error?

Check this answer, it might help you http://stackoverflow.com/a/28319156/2219600 — amalBit, Feb 04 '15 at 10:36

score 19 · Accepted Answer · edited May 23 '17 at 12:33

19

Please see this thread "Conversion to Dalvik format failed with error 1" on external JAR

more information here: Reason of Conversion to dalvik format failed with error 1

edited May 23 '17 at 12:33

Community

1
1

answered Jul 13 '11 at 19:03

Vector

359
2
6

One of the solutions that came up on the second link was to delete the project and then import it back – YoKaGe Jul 13 '11 at 20:45
How would i do that exactly because if i delete it than how can i import it – YoKaGe Jul 13 '11 at 20:46
You can move the project's folder to another location outside your eclipse workspace, then create a new project with the same name and import each class and xml file one by one. It would be a pain, but may be the only fix. Have you tried removing the layout file with the tab view and see if the error goes away? – Vector Jul 15 '11 at 23:16
For me the issue was Proguard and was caused by adding this line: -keepattributes ** So that was probably not the ultimate root cause but definitely caused the problem and removing it fixed the problem. – Fraggle Aug 29 '12 at 16:21
Problem with Proguard. Removed it and problem resolved. – Smeet Apr 04 '15 at 04:07

mamuso · Answer 2 · 2011-10-22T12:46:39.387

14

For those of you reaching here in the last days (see this post date), the last upgrades to ADT 14 have been causing every android project which uses an android library project to fail building with that error. I've tried this solution and it worked for me.

Tu sum it up, if you are using android library projects:
Package Explorer, right-click->Remove From Build Path (ok to unlink), on all the XXX_src in your projects of your workspace.

edited Oct 22 '11 at 12:46

answered Oct 21 '11 at 15:29

mamuso

3,117
3
30
32

This and reimport the projects fixed the problem for me, after trying all the other proposed solutios. Thanks. – Michael Greifeneder Feb 03 '12 at 13:44
1

+1 You're the man! you're answer saved me after wasting 8 hours hitting my head on the screen! – Mohamed A.Karim Oct 24 '12 at 16:10

score 9 · Answer 3 · answered Aug 10 '11 at 03:27

9

Windows 7 Solution if you are obfuscating with ProGuard:

Confirmed the problem is caused by ProGuard command line in the file
[Android SDK Installation Directory]\tools\proguard\bin\proguard.bat

Edit the following line will solve the problem:

call %java_exe% -jar "%PROGUARD_HOME%"\lib\proguard.jar %*

to

call %java_exe% -jar "%PROGUARD_HOME%"\lib\proguard.jar %1 %2 %3 %4 %5 %6 %7 %8 %9

answered Aug 10 '11 at 03:27

Noah

15,080
13
104
148

1

Thanks! This is exactly what was going on on my Windows 7 64bit OS! :) – Jona Oct 11 '11 at 17:20

score 5 · Answer 4 · answered Feb 07 '12 at 12:50

5

Upgrade your Proguard to its latest version i.e., 4.7... Dowload the zip from http://sourceforge.net/projects/proguard/files/latest/download?source=files .... then copy the "lib" and "bin" folders from the zip to your sdk/tools/proguard/ to replace the default or say old "bin" and "lib" .... try exporting your project once again...

answered Feb 07 '12 at 12:50

Achin Kumar

777
6
11

worked for me! Cleaning was not... so maybe some people need to do this – reox Jun 28 '12 at 09:48

score 4 · Answer 5 · answered Nov 20 '11 at 23:45

4

I was getting this because I had manually added android.jar to the build libraries because it was saying it wasn't finding the android libraries. The fix was to...

Remove android.jar from the build libraries
Right click on the project, go to "Android Tools", and select "Fix Project Properties"

Hope this helps.

answered Nov 20 '11 at 23:45

Gaʀʀʏ

4,372
3
39
59

Something like this helped fix my issue. But I needed to clean after this. – arantius Sep 02 '13 at 23:34

score 3 · Answer 6 · edited May 23 '17 at 11:58

3

If you are using Android SDK tools revision 12, check this link: Android SDK tools revision 12 has problem with Proguard => error conversion to Dalvik format failed with error 1

Simply cleaning, reimporting, removing libs won't work! Replacing tools directory with v11 was the only solution for me!

edited May 23 '17 at 11:58

Community

1
1

answered Jul 26 '11 at 14:53

Mr. D

101
5

I had the same issue. Updating to Proguard 4.6 solved the problem (I also edited the batch files, though it seemed to work even without doing that). – Sven Viking Aug 26 '11 at 17:41

score 2 · Answer 7 · edited Jul 05 '12 at 09:31

2

delete <classpathentry kind="lib" path="libs"/> from .classpath file.

this works for me.

edited Jul 05 '12 at 09:31

McDowell

107,573
31
204
267

answered Jul 05 '12 at 09:21

Savas Adar

4,083
3
46
54

Julia · Answer 8 · 2012-03-11T19:31:58.637

Had same problem after upgrade to Eclipse Indigo. The whole errors list started with

 [dx] java.lang.IllegalArgumentException: already added: <some library>;

and ended with

  Conversion to Dalvik format failed with error 1

The solution:

Right-click on project and select "Properties"
Select "Java Build Path" on left tree
Select "Library" tab on top
You will, probably see this library in the list (it is not jar, but Library!, the jar is below)
Delete it.

score 1 · Answer 9 · answered Apr 17 '12 at 17:18

1

i had the same problem and spent a lot of time trying everything i could, so the only way that worked for me was upgrading ADT to the latest version. So if nothing from the top helps to you just go Help->"Check for Updates".

answered Apr 17 '12 at 17:18

Ezeki

149
1
2

score 1 · Answer 10 · answered Oct 03 '11 at 14:35

1

This issue comes due to some conflicts in the jar which you might have added in the class path. Try removing the specific jar (hit and trail) and see if the error goes off.

answered Oct 03 '11 at 14:35

user976873

11
1

score 0 · Answer 11 · answered Oct 29 '12 at 21:48

0

While setting up the DropBox example app, I encountered this error.

The solution was to remove all JAR files from the build path, delete everything inside /libs, paste the required JAR files back in, and add them to the build path again.

answered Oct 29 '12 at 21:48

Andrew Calder

451
4
8

score 0 · Answer 12 · answered Feb 03 '13 at 10:50

0

Removed all the projects from workspace
Import projects back
Clean

worked !

answered Feb 03 '13 at 10:50

kakopappa

5,023
5
54
73

score 0 · Answer 13 · answered Nov 25 '11 at 06:35

0

Two easy steps:

CLEAN
BUILD

answered Nov 25 '11 at 06:35

Jayson Tamayo

2,741
3
49
76

Conversion to Dalvik format failed with error 1 Solution?

13 Answers13

Linked

Related