Bouncy castle runtime issue about certificate-transparency-android

[lubbo]

Actually it wasn’t a bug for me.
We were using 2 libs (certificate-transparency-android and another one). They imported the same bouncycastle lib as dependency. That generated a duplicate import.
To resolve the problem we excluded bouncycastle lib dependency for c-t-android in the gradle config.
Later we removed the other lib from the project keeping only c-t-android, but we forgot to remove also the exclusion in the gradle config.
So c-t-android dependency to bouncycastle was not found!
Removing the exclusion from gradle config made it working.

[mattmook]

Hi @sahil994 would it be possible to see what version of bouncy castle the app is compiling with by executing something like ./gradlew app:dependencies?

[lubbo]

We had the same problem.
We figured out we excluded some bouncycastle libs in the App gradle.

[mattmook]

hi @lubbo, could you expand on your solution a little more? Unfortunately I've not been able to reproduce the original bug so I wasn't even quite sure what was causing the issue in the first place, my own initial thought being an issue with Multidex.