Android Dex: UNEXPECTED TOP-LEVEL EXCEPTION: Alrea

问题:

My app depends on a library project. This library project depends on the Android Compatibility Package V4. I have NOT exported the library project's dependency. In my own project, I've added ACL V13 as a dependency, but when compiling I get the error that essentially there's a duplicate dependency. I thought not exporting the library project's dependency would resolve this issue, but it's not.

How can I resolve this?

EDIT

Also, according to Android tools docs:

Special case for android-support-v4.jar and android-support-v13.jar.

We make a special case for these two libraries because -v13 contains a full version of -v4 inside. If both are found, then only -v13 will be used.

So it should just work...

回答1:

If you use exactly the same lib jar in different projects (libs project or standard projects), the apk tools get rid automatically of the duplicate ones.

The problem starts when you have two libs with the same name but not at the same revision.

The android-support-v4.jar and android-support-v13.jar files can be from different revision since there always have the same name in different support package release (http://developer.android.com/tools/extras/support-library.html#Notes)

I would check that you use exactly the same revision of the support libs in your main project and in your lib project.

To make sure, copy the two support libraries jars (located in the android-sdk folder) to your projects libs folder.

{android-sdk}/extras/android/support/v4/android-support-v4.jar
AND
{android-sdk}/extras/android/support/v13/android-support-v13.jar

It should get rid of the problem.

回答2:

Delete the v4 package from the library.

Clean the Projects.

回答3:

In my case, I had just updated one of the JARs in the libs/ folder to a new version.

All it took to fix it was to run Build -> Rebuild Project, i.e. issue a 'clean' task before the 'assembleDebug' etc.

回答4:

Well, in my story I had to delete module dependencies which were the same, add it in library, and then add this library to each module as a dependence.

So:

• Module a : Depends on android-v4 (and has it in it's lib folder)

• Module b : Depends on android-v4 (and has it in it's lib folder)

  1. Add to libraries of project "android-v4" (for ex from 1st module). Delete it in module b lib folder.

  2. Delete in modules a and b dependence of android-v4

  3. Add to each module dependence -> library -> android-v4 (which you created in 2 step)

I'm not sure if it is the right solution but it works.

回答5:

Have you tried to change the dependency of the library from v4 to v13 and export it?

回答6:

Sometimes simply removing v4 support library does not work, you also need to rebuild or the project.