# Coverage for Android Instrumentation across mutli module project

**URL:** <https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600>\
**Category:** Bug Fixes\
**Created:** [October 14, 2019, 8:37am UTC](https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600 "2019-10-14T08:37:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![macgills](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@macgills](https://community.codecov.com/u/macgills)\
**Post date:** [October 14, 2019, 8:37am UTC](https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600/1 "2019-10-14T08:37:49Z")

</div>

### Description

I am failing to upload coverage for my “core” android library module with the tests being present in my “app” module, GitHub issue [here](https://github.com/codecov/codecov-bash/issues/210)

### Repository

> **[GitHub - kiwix/kiwix-android: Kiwix for Android](https://github.com/kiwix/kiwix-android)**
>
> Kiwix for Android

### Steps to Reproduce

1. Run a build for the modularisation branch
2. After success see a 28% decrease in project coverage in the report

**Expected behavior:** A merged coverage report for all modules incorporating unit & instrumentation tests

**Actual behavior:** Only unit test coverage uploaded

**Flakiness?** All the time

### Versions

n/a

### Additional Information

It could be possible that jacoco does not support this but I am not well versed in its functionality as I usually just install a plugin and run a gradle task. Any help in alleviating this problem would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\
**Post date:** [October 14, 2019, 3:16pm UTC](https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600/2 "2019-10-14T15:16:53Z")

</div>

Jacoco has a time stamp on the report, and if you are using a CI provider like Jenkins you may be uploading cached reports which Codecov would ignore as expired.

Can you clone the bash uploader step and add `-d` so you can examine the uploads (clone because -d won’t upload) to view the timestamps and ensure you are uploading them and they are not expired? (more then 12 hours old)

---

<div class="post-metadata">

**Author:** ![macgills](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@macgills](https://community.codecov.com/u/macgills)\
**Post date:** [October 14, 2019, 3:21pm UTC](https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600/3 "2019-10-14T15:21:01Z")

</div>

@drazisil I doubt that is happening as my report was uploaded [here](https://codecov.io/gh/kiwix/kiwix-android/tree/b23dcab0eccf7e27381c7ef53b5a4bcb1bae4fcf) as linked by this [travis build](https://travis-ci.org/kiwix/kiwix-android/builds/595126995)

---

<div class="post-metadata">

**Author:** ![macgills](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@macgills](https://community.codecov.com/u/macgills)\
**Post date:** [October 17, 2019, 11:08am UTC](https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600/4 "2019-10-17T11:08:21Z")

</div>

This isn’t actually a bug with codecov but I was just hoping somebody more knowledgeable than I would know how to fix this situation. I have created a repro project on GitHub [here](https://github.com/macgills/MultiModuleCoverageIssue) if that is of any help

---

<div class="post-metadata">

**Author:** ![macgills](https://avatars.discourse-cdn.com/v4/letter/m/ecae2f/32.png) [@macgills](https://community.codecov.com/u/macgills)\
**Post date:** [October 17, 2019, 2:37pm UTC](https://community.codecov.com/t/coverage-for-android-instrumentation-across-mutli-module-project/600/5 "2019-10-17T14:37:07Z")

</div>

[android - Is it possible for Instrumented tests to create coverage for a library module? - Stack Overflow](https://stackoverflow.com/questions/58415184/is-it-possible-for-instrumented-tests-to-create-coverage-for-a-library-module/58435071#58435071) TL:DR am idiot, all is well
