IssueTracker

Bug is reproducible. For more details, kindly refer - https://docs.google.com/document/d/1oWGh6swfjFIdli0D-HGKxkk6imI2PAuWgaSs9aXb5vM/edit (internal only link)

Can you please share any way to overcome this issue.

Hi Google Team -
I'm also facing this issue. Can we please prioritize this issue to fix?I can't get code coverage report with Android Test Orchestrator.

As comment # 3 mention, do we have any workaround? Code Coverage is an important parameter in our CI/CD.

Tried with gradle 3.4.0 "com.android.tools.build:gradle:3.4.0", still issue is replicable. Is there any work around to generate code coverage with test orchestrator enabled

This bug will be closed in 7 days. Please let us know how to respond to the external bug. Alternatively, please feel free to update the external bug directly. If an update is not provided, the external bug will be closed as infeasible.

Please ignore above comment.

Any update on the issue

I am also facing the same issue , when are we expecting to get it fixed

Team google, can you please provide fix or a workaround to generate code coverage report when we are clear app data?

Team, This looks to be a critical bug on Android test orchestrator. Kindly increase its priority and provide your comments.

Hi, I'm facing the same issue. Do you have any update on this?

I'm using:

execution 'ANDROIDX_TEST_ORCHESTRATOR' (version 1.2.0)
testInstrumentationRunnerArguments clearPackageData: 'true'

And the coverage files are not found after the test execution.
I need to use Android Test Orchestrator and clearPackageData to avoid crashes and random failures during the execution. But I also need to get coverage results.

Is there a way to save the coverage files in another location to avoid its removal? I tried to use coverageFilePath but it didn't work.