ID: dcd15c75-ad5b-49c3-b387-2d2faf6e7dcd
Hey @DGMohamadMlaies, I have moved this post into a new thread because the one where you initially posted was a totally different issue, and the user in that post is probably not particularly interested in this follow-up.
That being said, I had a look at the logs and found more about why the analysis failed. Your project was analyzed as a .NET project even though your repo is ~95% TypeScript, because there’s a .csproj file present at the repo root (with 0 bytes of actual code in it). Our service tried to build/analyze that .csproj, found nothing real to build, and failed with:
"SonarScanner for .NET integration failed: SonarQube was unable to collect the required information about your projects."
Fix: remove or rename that stray .csproj file if it isn’t meant to be built. If it’s a legitimate .NET component you do want analyzed, switch to CI-based analysis instead of Autoscan, so you can run an actual dotnet build between the scanner’s begin/end steps.