Closed Thangiee closed 10 years ago
Could you please copy/paste me the dependancy section of your build.gradle file?
I'm using scala and this sbt plugin so i'm not sure if that could be affecting this in some way. But anyhow, here are the dependencies from my build.sbt .
libraryDependencies ++= Seq(
"org.scaloid" %% "scaloid" % "3.4-10",
"com.android.support" % "support-v13" % "19.+",
"com.android.support" % "support-v4" % "19.+",
"com.android.support" % "appcompat-v7" % "19.+",
"com.google.code.gson" % "gson" % "2.2.4",
"com.github.amigold.fundapter2" % "library" % "1.01",
"de.keyboardsurfer.android.widget" % "crouton" % "1.8.4",
"de.greenrobot" % "eventbus" % "2.2.1",
"com.github.nscala-time" %% "nscala-time" % "1.2.0",
"org.jsoup" % "jsoup" % "1.7.3",
"ch.acra" % "acra" % "4.5.0",
aar("com.github.gabrielemariotti.changeloglib" % "library" % "1.5.1"),
aar("de.psdev.licensesdialog" % "licensesdialog" % "1.5.0"),
aar("com.google.android.gms" % "play-services" % "5.0.+"),
aar("com.anjlab.android.iab.v3" % "library" % "1.0.+"),
aar("com.github.dmytrodanylyk.circular-progress-button" % "library" % "1.1.0"),
aar("net.simonvt.menudrawer" % "menudrawer" % "3.0.6"),
aar("com.github.gabrielemariotti.cards" % "library-extra" % "1.8.0"),
aar("info.hoang8f" % "android-segmented" % "1.0.2"),
aar("com.makeramen" % "roundedimageview" % "1.3.0"),
aar("com.pixplicity.easyprefs" % "library" % "1.3"),
aar("fr.nicolaspomepuy" % "discreetapprate" % "1.0.5"),
aar("com.github.johnkil.android-progressfragment" % "progressfragment-native" % "1.4.0"),
aar("com.astuetz" % "pagerslidingtabstrip" % "1.0.1"))
If you remove the line corresponding to my lib, the manifest merger issue is gone?
Yes that is correct. If i remove it or use v1.0.5, it works. However, i just ran into a similar issue with another library. Maybe the issue is from my side? So i'll stick to 1.0.5 for the moment. Also, feel free to close the issue for now.
Thanks for your time.
When i update from version 1.0.5 to 2.0.2, i am getting this:
It seems like this library is pulling in the latest android support revisions.
Could it be that the "+" is causing it to do that?