It seems to be quite clear that there is a duplicate library somewhere that is also used in the com.gordonwong:material-sheet-fab:1.2.1 library But for the life of me I cannot figure out what or where and how to exclude it.

Help will be very much appreciated.

EDIT:

As suggested by crickets_007 in the comments (i think), I have run a dependancy report by going to the Gradle projects window and navigating to MyAppName > :app > Tasks > android and double clicking on androidDependancies which produced the dependancy report at the following link:

http://pastebin.com/u8Rtm9uu

Unfortunately I am not sure how to use this and what to do with this information.

I have also removed the com.gordonwong:material-sheet-fab:1.2.1 line from the gradle and recompiled the project as asked in the comments section and it works 100% so the problem is definitely something within tht library. Question is what and how do I exclude it???

library as a dependancy. Checking its dependancies I found it included the

com.nineoldandroids:library:2.4.0.

DING DING!! What further made this interesting and was that the source on github is

ArcAnimator/sample/src/main/java/io/codetail/arcsample/

This looks very similar to my error.

The nineoldandroids library is a library is a name I have seen many times in threads about related "clashing" issues. I started to look deeper into my other libraries.

What sealed the deal was when I looked into the other libraries that I include. Upon drilling into the

com.unipiazza.materialtwostepslogin:materialtwostepslogin:0.1.4

library I noticed that it includes the

com.github.ozodrukh:CircularReveal:1.1.1@aar

library. When browsing this library there is a source path on github which looks like this:

CircularReveal/circualreveal/src/main/java/io/codetail/

You will notice that this also looks similar to my error.
I went back to the inital library

com.gordonwong:material-sheet-fab:1.2.1

as I have now found my two conflicting libraries. I checked the issues tab to see if I have previously missed something but alas, this page was fruitless. I then noticed someone did a pull request and went to that tab (I was feeling lucky. Maybe this guy fixed it). AND BINGO: