Debricked always fails in AzureDevops

[johnstaveley]

I am trying to run debricked on my .net project. I always receive the following errors:

Scanner started...
Integration: azureDevOps
Working directory: /home/vsts/work/1/s
✗ Resolving AcceptanceTests/AcceptanceTests.csproj: failed
✗ Resolving Api.IntegrationTests/Api.IntegrationTests.csproj: failed
✗ Resolving Api.UnitTests/Api.UnitTests.csproj: failed
✗ Resolving Api/Api.csproj: failed
✗ Resolving Common.UnitTests/Common.UnitTests.csproj: failed
✗ Resolving Common/Common.csproj: failed
✗ Resolving MongoData/MongoData.csproj: failed
✗ Resolving Test.Common/Test.Common.csproj: failed
✗ Resolving Web.UnitTests/Web.UnitTests.csproj: failed
✗ Resolving Web/Web.csproj: failed
✗ Resolving Web/wwwroot/lib/blueimp-file-upload/bower.json: failed
✓ Resolving Web/wwwroot/lib/chosen-1.8.7/composer.json: done
✓ Resolving Web/wwwroot/lib/jquery-ui/package.json: done

...

MongoData/MongoData.csproj

• Critical: installing dependencies failed
  No specific documentation for this problem yet. If you would like this message to more informative for this error, please create an issue here: https://github.com/debricked/cli/issues
  /usr/bin/dotnet restore MongoData.csproj --use-lock-file --lock-file-path packages.lock.json

...

##[error]Bash exited with code '1'.
Finishing: Debricked scan

I assume this is causing the debricked process to fail. However if I look in debricked it analyses the dependencies ok.

My Azure Devops build pipeline:

trigger:
branches:
include:
- '*' # Run on all branches
exclude:
- 'master' # Excluding master as we do not use this

resources:
- repo: self

stages:
- stage: Test
displayName: Test
jobs:
- job: Test
displayName: Debricked scan
pool:
vmImage: 'ubuntu-latest'
steps:
- script: |
curl -LsS https://github.com/debricked/cli/releases/download/release-v2/cli_linux_x86_64.tar.gz | tar -xz debricked
./debricked scan
displayName: Debricked scan
env:
DEBRICKED_TOKEN: $(DEBRICKED_TOKEN)
EXCLUDED_DIRECTORIES: "Api.UnitTests,Common.UnitTests,Web.UnitTests"

This used to work a long time ago. Why not now?