We are having a similar issue. But switching to the coverage.json file instead of .resultset.json solved it for us. Was there some change on sonarcloud to no longer be compatible with the previous file?
We are having a similar issue. But switching to the coverage.json file instead of .resultset.json solved it for us. Was there some change on sonarcloud to no longer be compatible with the previous file?