After adding code coverage, i can't see my file anymore

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
    Azure Devops
  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
    Azure devops
  • Scanner command used when applicable (private details masked)
    • task: SonarCloudPrepare@1
      SonarCloud: ‘SonarCloud For ESG’
      organization: ‘sonarcloudtools’
      scannerMode: ‘MSBuild’
      projectKey: ‘$(projectName)’
      projectName: ‘$(projectName)’
      extraProperties: |
  • task: SonarCloudAnalyze@1

    • task: SonarCloudPublish@1
      pollingTimeoutSec: ‘300’
  • Languages of the repository
  • Only if the SonarCloud project is public, the URL
    private sonar
    • And if you need help with pull request decoration, then the URL to the PR too
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
    The code coverage and the sonar are goodd, but if i want to view the file in my sonar interface, i can’t . I have the following message: “The file was removed, no source code can be displayed.”
  • Steps to reproduce
    i don’t understand
  • Potential workaround
    i didn’t find

Hey there.

What link are you clicking on that takes you to this message?

Hello and thanks,

I’m clicking on the bug for sample, there is a message of the defect, then when you click, you access to the source code with the defect line.

The source code don’t display, and i have this error message.


Hello @VGIb ,

I’m trying to check our logs to understand the issue that you have. However, I’m not able to find the request related to the action of displaying the issue in BaseRequestBuilder.cs file.
If you still have the problem, I would ask you to reproduce the behavior in SonarCloud and ping me with a date to be able to check deeper into the logs.

Thanks in advance,

Hey @VGIb,

Could you please check if your logged user has “See Source Code ” permission in your project => Administration => Permissions? it can be the reason for the error you have.



this was the problem. Seems the error message is wrong.



This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.