Has anyone else run into numerous problems with `j...

# android

[Bradleycorn]

Has anyone else run into numerous problems with jacoco since updating Android Studio to version 4.2.1?
First I could not run unit tests at all, they would error with class not found errors. I was able to resolve that by excluding jdk internal classes (jacoco.excludes = ['jdk.internal.*']). But now my coverage reports show 0% coverage, and I get a bunch of build output messages saying that “execution data for class  xyz does not match”.  I cant’ figure out how to solve that one?

It seems to be something in the AGP. If I roll the AGP back to v4.1.3 everything works fine. But as soon as I update to 4.2.0 suddenly I get 0% in my coverage report along with the “execution data for class…” warnings in the build output.

[kevindmoore]

Yeah, I think I updated my version and had problems too. I had to stream my testing all the way back to the bare bones to get things working again

[kevindmoore]

I am currently just using 4.1.0

[Bradleycorn]

hmm … perhaps I should file a defect.

[Bradleycorn]

@kevindmoore - question for you … do you use Firebase in your app (specifically the performance monitoring plugin)? … I have found that to be the source of my problems.

[kevindmoore]

I am not

[Bradleycorn]

hmm OK. I have found that to be the culprit in my case.