# No code coverage in SonarCloud (all seems to be configured correctly)

**URL:** <https://community.sonarsource.com/t/no-code-coverage-in-sonarcloud-all-seems-to-be-configured-correctly/13566>\
**Category:** SonarQube Cloud\
**Tags:** msbuild, azuredevops-services, dotnet, sonarqube-cloud, coverage\
**Created:** [August 26, 2019, 6:21am UTC](https://community.sonarsource.com/t/no-code-coverage-in-sonarcloud-all-seems-to-be-configured-correctly/13566 "2019-08-26T06:21:58Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![DHoefakker](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dhoefakker/32/5083_2.png) [@DHoefakker](https://community.sonarsource.com/u/DHoefakker)\
**Post date:** [January 16, 2020, 7:30am UTC](https://community.sonarsource.com/t/no-code-coverage-in-sonarcloud-all-seems-to-be-configured-correctly/13566/29 "2020-01-16T07:30:48Z")

</div>

To all who encounter this issue, with help of @mickaelcaro and some updates to the SonarCloud vso tasks, we found the issue.

In my case the property “/p:PathMap” in the build task caused it, when removed i do see the code coverage showing up in SonarCloud.

---

_[View the full topic](https://community.sonarsource.com/t/no-code-coverage-in-sonarcloud-all-seems-to-be-configured-correctly/13566)._