Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JAR packages conflicts #143

Closed
oyty opened this issue Apr 14, 2015 · 4 comments
Closed

JAR packages conflicts #143

oyty opened this issue Apr 14, 2015 · 4 comments
Assignees
Labels

Comments

@oyty
Copy link

oyty commented Apr 14, 2015

when I build the app, it got follow error message:
image

when I search the class AnimRes
image
you could find the class AnimRes comes from two places, the V4 package and the support-annotations package, the V4 is in my libs, but I can't find the support-annotations package, I think it is a dependance of the fresco library. The possible way to solve this problem is to delete the V4 package, but I need it, the V4 package contains two items, annotations and v4, i need v4, but i can't just delete the annotations item, what should I do?
My dependances:
image

@tyronen tyronen self-assigned this Apr 14, 2015
@tyronen
Copy link
Contributor

tyronen commented Apr 14, 2015

We have a pending commit that should fix this.

@tyronen tyronen added the build label Apr 14, 2015
@andforce
Copy link

@oyty : Before @tyronen fix, you can try this:
compile ('com.facebook.fresco:fresco:0.1.0+'){
exclude group: 'com.android.support', module: 'support-v4'
exclude group: 'com.android.support', module: 'appcompat-v7' }

if you have used nineoldandroids,also you can try this:

compile('com.nineoldandroids:library:2.4.0') {
    exclude group: 'com.android.support', module: 'support-v4'
    exclude group: 'com.android.support', module: 'appcompat-v7'
}

@tyronen
Copy link
Contributor

tyronen commented Apr 15, 2015

The most recent head should take care of this issue. Let us know if it doesn't.

@tyronen tyronen closed this as completed Apr 15, 2015
@oyty
Copy link
Author

oyty commented Apr 15, 2015

@andforce ,yeah, I fix it. I just delete the v4 package use the one that fresco is dependent on. And i said i need my v4 package before because of some problem else. i have to point out that when we use the fresco, we have to pay attention to the dependences library, and some classes of them can't be mixed up, you should to keep them in the proguard file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants