I am maintaining and Android app that now suffers from an unsafe X509 TrustManager implementation. Since the app doesn't make any HTTPS calls except through dependencies, one of the dependencies is causing the issue.The problem is that I don't know what any of these dependencies are for (there are ~20) except for one, which is a simple social (Facebook, Twitter) button library. I looked through the source code of that one, because it was small enough, and it's not the issue.Some of the dependencies are packaged through Maven so I can't browse their source, and some of them are no longer on Github (the library was OS, but eventually scrapped).Many of the dependencies make HTTP(S) requests, which is causing the X509TrustManager error. How can I figure out which one is causing the error without having the source?
How can I track down a dependency that is causing an X509TrustManager error without having the source?
debugging;dependencies;dependency management
If you really have no better clues than delete and test I suggest a binary search.  Spend 1.5 * 10 hours getting rid of half of the dependencies.  Then test and see if it's in that half.  Lather rinse, repeat until you're down to one suspect dependency. Save it in the different states so you can go back without it being a pain.  Document it well.  Sucks to go down this rabbit hole for hours and then get lost.Should take no more than 1.5 * 10 + 4.5 +1.5 * 5 + 4.5 +1.5 * 3 + 4.5 +1.5 * 2 + 4.5 +1.5 * 1 + 4.5 = 54 hours. Better than 120 I guess.Sure there are no better clues?