I am assuming the project you've worked on has been around for some time, I've seen some badly setup android/iOS configurations for some of the Flutter projects that I've worked on.

Let's try to understand what testDebugUnitTest does first:

1. testDebugUnitTest is a Gradle task that runs the local unit tests (the ones under android/app/src/test/java/...) for the Debug build variant of your Android app.

2. These tests are JVM unit tests (not Flutter/Dart tests). They run on your development machine, without an Android device or emulator.

So, `testDebugUnitTest` is how the Gradle handles Flutter. And Flutter generates those files and most commonly if a generated functionality is causing issues, maybe the best course of action is to re-generate that folder. You can re-create your android folder like this:

flutter create --platforms=android .

I already encountered a lot of threads that are related to testDebugUnitTest issues.

Does this issue come from only the aforementioned packages or does it happen from other packages as well?